January 2023 Endgame

[roblourens]

• 1/23 Code freeze for the endgame
• 1/27 Endgame done
• 2/2 Expected release date (this may change)

Monday

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

Tuesday

• [x] 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
• [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

Thursday

• [x] Fixing (self-assigned, milestone assigned, no need for PR or review)
  • 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
• [x] 🔖Verification needed
• [x] 🔖Verification

Friday

• [x] Build a stable build to ensure stable build is green @roblourens
• [x] Pause scheduled insider builds (includes vscode.dev publishing) @roblourens
• Satellite modules/npm packages ready, version updated, smoke tested
  • [x] yo generator @aeschli
  • [x] js-debug @connor4312
  • [x] Debug Adapter Protocol @connor4312
  • [x] vscode-debugadapter-node @roblourens
  • [x] Mock Debug @roblourens
  • [x] vscode-test-web @aeschli
• [x] Only candidate issues are open and assigned to 🔖milestone
• [ ] All issues 🔖verified
• [x] All open PRs on the milestone 🔖merged or deferred
• [x] Branch code to release/<x.y> after all expected fixes are in (latest 5PM PST) @roblourens
• [x] Branch distro to release/<x.y> after all expected fixes are in (latest 5PM PST) @roblourens
• [x] Branch vscode.dev to release/<x.y> after all expected fixes are in (latest 5PM PST) @roblourens
• [x] Bump up the version in package.json on main - @roblourens
• [x] 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) @roblourens
• [x] 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 @roblourens
• [x] Announce main is open for business @roblourens
• [x] Fixing (PR + review required once branched - 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
  • [x] @aeschli
  • [ ] @alexdima
  • [x] @alexr00
  • [ ] @andreamah
  • [ ] @bhavyaus
  • [x] @bpasero
  • [x] @chrmarti
  • [x] @connor4312
  • [x] @dbaeumer
  • [ ] @deepak1556
  • [x] @egamma
  • [ ] @hediet
  • [x] @isidorn
  • [x] @joaomoreno
  • [x] @joyceerhl
  • [x] @jrieken
  • [x] @kieferrm
  • [x] @lramos15
  • [x] @lszomoru
  • [ ] @meganrogge
  • [x] @mjbvz
  • [x] @rebornix
  • [x] @roblourens
  • [x] @rzhao271
  • [ ] @sandy081
  • [ ] @sbatten
  • [ ] @tanhakabir
  • [x] @tylerleonhardt
  • [ ] @tyriar
• [x] Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the @roblourens can generate the pull request acknowledgment for all repositories at once. @roblourens
  • [x] 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
• [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] Build and manually release Insider from release/<x.y> for Code @roblourens
  • [x] Build and manually release Insider from release/<x.y> for vscode.dev (if required) @roblourens

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> @roblourens
• [x] Build Insider from release/<x.y> @roblourens
• [x] Manually release Insider @roblourens
• [x] Build stable for all platforms as new candidate issues come in @roblourens
• [ ] Documentation updated
  • [x] @aeschli
  • [ ] @alexdima
  • [ ] @alexr00
  • [ ] @andreamah
  • [ ] @bhavyaus
  • [x] @bpasero
  • [x] @chrmarti
  • [x] @connor4312
  • [x] @dbaeumer
  • [ ] @deepak1556
  • [ ] @egamma
  • [ ] @hediet
  • [x] @isidorn
  • [x] @joaomoreno
  • [x] @joyceerhl
  • [ ] @jrieken
  • [x] @kieferrm
  • [x] @lramos15
  • [x] @lszomoru
  • [ ] @meganrogge
  • [x] @mjbvz
  • [x] @rebornix
  • [ ] @roblourens
  • [x] @rzhao271
  • [ ] @sandy081
  • [ ] @sbatten
  • [x] @tylerleonhardt
  • [ ] @tyriar
• [x] Run scripts/test-documentation.sh|bat and add file or fix issues if there are new colors that are not documented. @roblourens

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

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

• [x] Build stable for all platforms @roblourens
• [x] Sanity check of installable bits (server instructions)
  • [x] Windows 32 bit @rzhao271
  • [x] signed installer 32-bit
  • [x] signed user installer 32-bit
  • [x] zip 32-bit
  • [x] server 32-bit
  • [x] cli 32-bit
  • [x] Windows 64 bit owner
  • [x] signed installer 64-bit @joyceerhl
  • [x] signed user installer 64-bit @joyceerhl
  • [x] zip 64-bit @joyceerhl
  • [x] server 64-bit @rzhao271
  • [x] cli 64-bit @joyceerhl
  • [x] Windows ARM64 @sandy081
  • [x] signed installer ARM64
  • [x] signed user installer ARM64
  • [x] zip ARM64
  • [x] cli ARM64
  • [x] macOS
  • [x] Intel + Universal @lramos15
  • [x] cli Intel @roblourens
  • [x] Apple Silicon + Universal @kieferrm
  • [x] cli Apple Silicon @kieferrm
  • [x] Linux x64
  • [x] deb @connor4312
  • [x] rpm @rzhao271
  • [x] archives @connor4312
  • [x] snap (sudo snap install --classic --dangerous <file>.snap) @connor4312
  • [x] cli @connor4312
  • [x] Linux server owner
  • [x] x64 @roblourens
  • [x] x64 Alpine @rzhao271
  • [x] ARM32 @roblourens
  • [x] ARM64 @roblourens
  • [x] ARM64 Alpine @rzhao271
• [x] Publish website @gregvanl
• [x] Publish to stable @roblourens
• [x] Trigger the vscode.dev Deploy pipeline for the prod deployment target. Request approval from another team member at the necessary step. @roblourens
• [x] Create an official release @roblourens
  • [x] Create a tag (make sure you pull the release branch first): 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. Also change the relative links for the key highlight list items to absolute links Example
• [x] Twitter announcement @chrisdias
• [x] Enable scheduled insider builds @roblourens
• [x] Publish @types/vscode @roblourens
• [x] Close the milestone on GitHub @roblourens
• [x] If no Patch Tuesday release is planned, let the Updates team know of that fact (CSEClientPatching@microsoft.com) @roblourens
• [x] If a recovery build is needed, proceed to https://github.com/microsoft/vscode/wiki/Endgame-Recovery-Template or https://github.com/microsoft/vscode-internalbacklog/wiki/Patch-Tuesday-Release-Endgame-Template/ @roblourensj

[lorand-horvath]

@roblourens Maybe I don't understand it, but I see you checked the Friday task Bump up the version in package.json on main as completed. However, the version in the file is still at 1.75.0 https://github.com/microsoft/vscode/blob/main/package.json Shouldn't it say 1.76.0 already?

I've mentioned this problem before, in the October 2022 Endgame https://github.com/microsoft/vscode/issues/164400#issuecomment-1297202242 and at the time it was taken care of by @rebornix and @joaomoreno

[roblourens]

Thanks @lorand-horvath, I must have missed it while multitasking