• 5/29 Code freeze Zurich for the endgame
• 6/1 Code freeze Redmond for the endgame
• 6/5 Endgame done
• 6/10 Expected release date (this may change)

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

Monday

• Run OSS tool endgame lead
• Code freeze at 5pm PT
• Ensure we have a green build on all platforms at 5pm PT
• Create test plan items following the template here by 6pm PT
• Add verification-needed label to features needed testing and are not tested by TPIs.
• Update your availability for testing here - https://vscode-tools.azurewebsites.net/
• Create Test plan item for smoke testing (template) endgame lead
• Review the extensionKind list in product.json both for stable and insiders, see this tracking issue @egamma

Tuesday

• Test plan items assigned (using https://vscode-tools.azurewebsites.net/)
  • Run the tool multiple times to balance load if test items come in later and assignments are already made
  • Assigned to you
• 🔖All closed feature-requests either have a verification-needed or on-testplan label
• 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
• Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame lead

Thursday

• Fixing (self-assigned, milestone assigned)
• 🔖Verification needed
• 🔖Verification
• Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test and fixed endgame lead

Friday

• Pause scheduled insider builds endgame lead
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno
  • node debug @weinand
  • node debug2 @roblourens
  • js-debug @connor4312
  • node debugadapter node @weinand
  • custom data for html/css @aeschli
• All issues 🔖verified
• Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
  • Windows - @joaomoreno
  • macOS - @isidorn
  • Linux - @dbaeumer
  • Web (Chromium) - @alexr00
• All release notes updated
  • release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
  • @aeschli
  • @alexdima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @connor4312
  • @dbaeumer
  • @deepak1556
  • @eamodio
  • @egamma
  • @isidorn
  • @JacksonKearl
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @lszomoru
  • @mjbvz
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @Tyriar
  • @weinand
• Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. Use the thankyou tool to generate the initial contents of the section. owner
  • vscode endgame lead
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-debugadapter-node @weinand
  • vscode-js-debug @connor4312
  • vscode-languageserver-node @dbaeumer
  • language-server-protocol @dbaeumer
  • vscode-textmate @alexdima
  • vscode-loader @alexdima
  • vscode-generator-code @aeschli
  • vscode-vsce @joaomoreno
  • vscode-docs @gregvanl
  • vscode-css-languageservice @aeschli
  • vscode-json-languageservice @aeschli
  • vscode-html-languageservice @aeschli
  • jsonc-parser @aeschli
  • vscode-eslint @dbaeumer
  • vscode-jshint @RMacfarlane
  • vscode-recipes @chrisdias
  • localization @weeteckt
  • vscode-github-issues-prs @chrmarti
  • inno-updater @joaomoreno
• Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. endgame lead
• Acknowledge issue trackers from the community @chrmarti
• Add notable fixes to the release notes all
• When done fixing/verifying and there are changes since last build at the end of day PT
  • Trigger new insider build and publish it manually endgame lead
• Branch code to `release/<x.y> endgame lead
• Bump up the version in package.json - endgame lead
• Announce master is open for business endgame lead

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> endgame lead
• Build Insider from release/<x.y> endgame lead
• Manually release Insider endgame lead
• Build stable for all platforms as new candidate issues come in endgame lead
• Documentation updated
  • @aeschli
  • @alexdima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @connor4312
  • @dbaeumer
  • @deepak1556
  • @eamodio
  • @egamma
  • @isidorn
  • @JacksonKearl
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @lszomoru
  • @mjbvz
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @Tyriar
  • @weinand
• Run scripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented.

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

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

• Build stable for all platforms endgame lead
• Sanity check of installable bits
  • Windows 32 bit @dbaeumer`
    • signed installer 32-bit
    • signed user installer 32-bit
    • zip 32-bit
  • Windows 64 bit @jrieken
    • signed installer 64-bit
    • signed user installer 64-bit
    • zip 64-bit
  • macOS - @weinand
  • Linux
    • deb package 64-bit @aeschli
    • rpm package 64-bit @chrmarti
    • archives @dbaeumer
    • snap (sudo snap install --classic --dangerous <file>.snap) @alexr00
  • Server (instructions) owner
    • Linux @aeschli
    • macOS @weinand
    • Windows @jrieken
• Publish website @gregvanl
• Publish Localization language pack @weeteckt
• Publish to stable endgame lead
• Create an official release endgame lead
  • Create a tag: 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. (Example, Recovery)
• Publish @types/vscode endgame lead
• Enable scheduled insider builds endgame lead
• Twitter announcement @chrisdias