• May 26 Code freeze for the endgame
• June 2 Endgame done
• June 8 Expected release date (this may change)

Friday

• Check that all queries in this issue use the current milestone @meganrogge
• Run OSS tool @meganrogge
• Update links in the Endgame notebooks to point to new milestone @meganrogge
• Code freeze at 5pm PT
• Ensure we have a green build on all platforms at 5pm PT
• 🔖All closed feature-requests either have a verification-needed or on-testplan label
• Create test plan items following the template here by 6pm PT
• Update your availability for testing here - https://tools.code.visualstudio.com/team-manifest team
  • Update availability of testers in vacation. Double check N/A testers. @meganrogge

Tuesday

• Test plan items assigned (using https://tools.code.visualstudio.com/test-plan-items)
  • Run the tool multiple times to balance load if test items come in later and assignments are already made
  • Assigned to you
• Test build starts at 7am CET
• Test plan ready by 8am CET
• 🔖Testing
• 🔖Verification needed

Wednesday

• 🔖Testing
• Remind team members to assign issues that they intend to fix to the current milestone
• Fixing (self-assigned, milestone assigned)
• 🔖Verification needed

Thursday

• Fixing (self-assigned, milestone assigned)
  • Increased scrutiny sets in due to testing being completed. Fixes pose a much higher risk
  • Move issues to the next month that can be deferred
• 🔖Verification needed
• 🔖Verification
• Make sure to have the insider build @meganrogge
• Pause scheduled insider builds (includes vscode.dev publishing) @meganrogge

Friday

• Branch & Release by latest 9AM CET @meganrogge
  • Branch following repositories to release/1.79
    • vscode
    • vscode-distro
    • vscode-dev
  • Build and manually release Insider from release/1.79 for Code
  • Build and manually release Insider from release/1.79 for vscode.dev (if required)
• Bump up the version in package.json on main - @meganrogge
• Localization: Run Update VS Code Branch build with release/* as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) @meganrogge
• Create next milestone and ensure that it has a due date. The created milestone and its due date will be automatically synced across our repos @meganrogge
• Announce main is open for business @meganrogge
• Build a stable build from release branch to ensure stable build is green @meganrogge
• Satellite modules/npm packages ready, version updated, smoke tested
  • yo generator @aeschli
  • js-debug @connor4312
  • Debug Adapter Protocol @connor4312
  • vscode-debugadapter-node @connor4312
  • Mock Debug @roblourens
  • vscode-test-web @aeschli
  • vsce @sandy081
• Only candidate issues are open and assigned to 🔖milestone
• All issues 🔖verified
• All open PRs on the milestone 🔖merged or deferred
• Fixing (PR + review required - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• All release notes updated
  • release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
• Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the @meganrogge can generate the pull request acknowledgment for all repositories at once. @meganrogge
  • debug-adapter-protocol, inno-updater, jsonc-parser, language-server-protocol, lsif-node, vscode, vscode-codicons, vscode-css-languageservice, vscode-debugadapter-node, vscode-dev-containers, vscode-docs, vscode-emmet-helper, vscode-eslint, vscode-extension-samples, vscode-generator-code, vscode-hexeditor, vscode-html-languageservice, vscode-js-debug, vscode-js-debug-companion, vscode-js-profile-visualizer, vscode-jshint, vscode-json-languageservice, vscode-languageserver-node, vscode-livepreview, vscode-loader, vscode-lsif-extension, vscode-node-debug, vscode-node-debug2, vscode-pull-request-github, vscode-recipes, vscode-references-view, vscode-textmate, vscode-vsce
• Acknowledge issue trackers from the community @chrmarti
• When done fixing/verifying and there are changes since last build at the end of day PT
  • Build and manually release Insider from release/<x.y> for Code @meganrogge
  • Build and manually release Insider from release/<x.y> for vscode.dev (if required) @meganrogge

Friday/Monday

• Polish release notes redmond
• Fixing (only critical bugs - no string changes)

Monday - Wednesday

• 🔖milestone issues
• 🔖candidate issues
• Polish release notes redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @meganrogge
• Build Insider from release/<x.y> @meganrogge
• Manually release Insider @meganrogge
• Build stable for all platforms as new candidate issues come in @meganrogge
• Documentation updated
• Run scripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented. @meganrogge

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame. @meganrogge

Wednesday/Thursday - Expected release day (this may change)

• Build stable for all platforms @meganrogge
• Sanity Testing
  • Windows 32 bit @connor4312
    • System Installer
    • User Installer
    • Archive
    • Server
    • CLI
  • Windows 64 bit @joyceerhl
    • System Installer
    • User Installer
    • Archive
    • Server
    • CLI
  • Windows ARM64 @TylerLeonhardt
    • System Installer
    • User Installer
    • Archive
    • CLI
  • macOS Intel @meganrogge
    • Archive
    • Universal Archive
    • Server
    • CLI
  • macOS ARM64 @bhavyaus
    • Archive
    • Universal Archive
    • Server
    • CLI
  • Linux x64 @andreamah
    • Archive
    • DEB
    • RPM @connor4312
    • Snap
  • Linux Server @amunger
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
  • Linux CLI @rzhao271
    • x64
    • ARM32
    • ARM64
    • x64 Alpine
    • ARM64 Alpine
• Publish website @gregvanl
• Publish to stable @meganrogge
• Trigger the vscode.dev Deploy pipeline for the prod deployment target. @meganrogge
  • Request approval from another team member at the necessary step to deploy the vscode.dev build. @meganrogge
• Create an official release @meganrogge
  • Create a tag (make sure you pull the release branch first): git tag <x.y.z>
  • Push the tag: git push origin <x.y.z>
  • Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Also change the relative links for the key highlight list items to absolute links Example
• Twitter announcement @chrisdias
• Enable scheduled insider builds @meganrogge
• Publish @types/vscode @meganrogge
• Close the milestone on GitHub @meganrogge
• If no Patch Tuesday release is planned, let the Updates team know of that fact (CSEClientPatching@microsoft.com) @meganrogge
• If a Recovery or Patch Tuesday release is needed proceed to running Recovery Release or Patch Tuesday Release @meganrogge