January 2021 Endgame

[lszomoru]

• January25 Code freeze for the endgame
• January/29 Endgame done
• February/3 Expected release date (this may change)

Monday

• [x] Run OSS tool @sbatten
• [x] Code freeze at 5pm PT
• [x] Ensure we have a green build on all platforms at 5pm PT
• [x] Create test plan items following the template here by 6pm PT
• [x] Add verification-needed label to features needed testing and are not tested by TPIs.
• [x] Update your availability for testing here - https://vscode-tools.azurewebsites.net/
• [x] Create Test plan item for smoke testing (template) @sbatten

Tuesday

• [x] 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
• [x] 🔖All closed feature-requests either have a verification-needed or on-testplan label
• [x] Test build starts at 7am CET
• [x] Test plan ready by 8am CET
• [x] 🔖Testing
• [x] 🔖Verification needed

Wednesday

• [x] 🔖Testing
• [x] Remind team members to assign issues that they intend to fix to the current milestone
• [x] Fixing (self-assigned, milestone assigned)
• [x] 🔖Verification needed
• [x] Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test-failure and fixed @sbatten

Thursday

• [x] Fixing (self-assigned, milestone assigned, NO discussion during standup)
  • Move issues to the next month that can be deferred
• [x] 🔖Verification needed
• [x] 🔖Verification
• [x] Prepare for Smoke test: Make sure all smoke test issues are labelled smoke-test-failure and fixed @sbatten

Friday

• [x] Pause scheduled insider builds @sbatten
• Satellite modules/npm packages ready, version updated, smoke tested
  • [x] vscode @eamodio
  • [x] yo generator @aeschli
  • [x] vsce @joaomoreno
  • [x] debug-adapter-protocol @weinand
  • [x] node debug @weinand
  • [x] node debug2 @roblourens
  • [x] js-debug @connor4312
  • [x] node debugadapter node @weinand
  • [x] custom data for html/css @aeschli
• [x] All issues 🔖verified
• [x] Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
  • [x] Windows - @sbatten
  • [x] macOS (Universal) - @roblourens
  • [x] Linux - @mjbvz
  • [x] Web (Chromium) - @RMacfarlane
• [ ] All release notes updated
  • release notes are collected in a file named v<Major>_<Minor>.md in this repo directory
  • [x] @aeschli
  • [x] @alexdima
  • [x] @alexr00
  • [x] @bpasero
  • [x] @chrmarti
  • [x] @connor4312
  • [x] @dbaeumer
  • [x] @deepak1556
  • [x] @eamodio
  • [ ] @egamma
  • [x] @isidorn
  • [ ] @JacksonKearl
  • [x] @joaomoreno
  • [x] @jrieken
  • [ ] @kieferrm
  • [x] @lramos15
  • [x] @lszomoru
  • [x] @meganrogge
  • [ ] @mjbvz
  • [ ] @rebornix
  • [x] @rmacfarlane
  • [ ] @roblourens
  • [x] @rzhao271
  • [x] @sandy081
  • [x] @sbatten
  • [x] @TylerLeonhardt
  • [ ] @tyriar
  • [x] @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
  • [x] vscode @sbatten
  • [x] debug-adapter-protocol @weinand
  • [x] vscode-node-debug @weinand
  • [ ] vscode-node-debug2 @roblourens
  • [x] vscode-debugadapter-node @weinand
  • [x] vscode-js-debug @connor4312
  • [x] vscode-languageserver-node @dbaeumer
  • [x] language-server-protocol @dbaeumer
  • [x] vscode-textmate @alexdima
  • [x] vscode-loader @alexdima
  • [x] vscode-generator-code @aeschli
  • [x] vscode-vsce @joaomoreno
  • [x] vscode-docs @gregvanl
  • [x] vscode-css-languageservice @aeschli
  • [x] vscode-json-languageservice @aeschli
  • [x] vscode-html-languageservice @aeschli
  • [x] jsonc-parser @aeschli
  • [x] vscode-eslint @dbaeumer
  • [x] vscode-jshint @rmacfarlane
  • [x] vscode-recipes @weinand
  • [x] localization @weeteckt
  • [x] inno-updater @joaomoreno
• [x] Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. @sbatten
• [x] Acknowledge issue trackers from the community @chrmarti
• [x] 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
  • [x] Trigger new insider build and publish it manually @sbatten
• [x] Branch code to release/<x.y> @sbatten
• [x] Bump up the version in package.json on master - @sbatten
• [x] Announce master is open for business @sbatten

Friday/Monday

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

Monday - Wednesday

• [x] 🔖milestone issues
• [x] 🔖candidate issues
• [x] Polish release notes redmond
• [x] Cherry-pick hand-picked and reviewed changes to release/<x.y> @sbatten
• [x] Build Insider from release/<x.y> @sbatten
• [x] Manually release Insider @sbatten
• [x] Build stable for all platforms as new candidate issues come in @sbatten
• [ ] Documentation updated
  • [x] @aeschli
  • [x] @alexdima
  • [ ] @alexr00
  • [ ] @bpasero
  • [x] @chrmarti
  • [ ] @connor4312
  • [x] @dbaeumer
  • [ ] @deepak1556
  • [x] @eamodio
  • [ ] @egamma
  • [x] @isidorn
  • [ ] @JacksonKearl
  • [x] @joaomoreno
  • [ ] @jrieken
  • [ ] @kieferrm
  • [x] @lramos15
  • [x] @lszomoru
  • [x] @meganrogge
  • [ ] @mjbvz
  • [ ] @rebornix
  • [ ] @rmacfarlane
  • [ ] @roblourens
  • [x] @rzhao271
  • [x] @sandy081
  • [ ] @sbatten
  • [x] @TylerLeonhardt
  • [ ] @tyriar
  • [x] @weinand
• [x] 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. @sbatten

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

• [x] Build stable for all platforms @sbatten
• [x] Sanity check of installable bits
  • [x] Windows 32 bit @connor4312
  • [x] signed installer 32-bit
  • [x] signed user installer 32-bit
  • [x] zip 32-bit
  • [x] Windows 64 bit @connor4312
  • [x] signed installer 64-bit
  • [x] signed user installer 64-bit
  • [x] zip 64-bit
  • [x] Windows ARM64 @joaomoreno
  • [x] signed installer ARM64
  • [x] signed user installer ARM64
  • [x] zip ARM64
  • [x] macOS @roblourens
  • [x] Intel owner
  • [x] Apple Silicon owner
  • [x] Linux x64 @RMacfarlane
  • [x] deb owner
  • [x] rpm owner
  • [x] archives owner
  • [x] snap (sudo snap install --classic --dangerous <file>.snap) owner
  • [x] Server (instructions)
  • [x] Linux @JacksonKearl
  • [x] macOS @roblourens
  • [x] Windows @JacksonKearl
• [x] Publish website @ornellaalt
• [x] Publish Localization language pack @weeteckt
• [x] Publish to stable @sbatten
• [x] Create an official release @sbatten
  • [x] Create a tag: git tag <x.y.z>
  • [x] Push the tag: git push origin <x.y.z>
  • [x] 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
• [x] Publish @types/vscode @sbatten
• [x] Enable scheduled insider builds @sbatten
• [x] Twitter announcement @chrisdias

[andreialecu]

Don't mean to spam this. Just want to make sure it's acknowledged:

The February release seems to officialise macOS arm64 builds (for Apple Silicon M1 chips).

However, macOS 11.2 was just released yesterday and it breaks arm64 builds of nodejs: https://github.com/nodejs/node/issues/37061 (this has been confirmed)

Additionally, it also breaks arm64 VSCode insiders versions: https://github.com/microsoft/vscode/issues/113410#issuecomment-771153250 so Electron is also affected.

Unless a solution is found quickly, I think the arm64 release timeline may need to be reassessed.

[deepak1556]

Apple silicon stable release will be delayed for another iteration to accommodate the fix for https://github.com/microsoft/vscode/issues/115646, sorry all!