Closed
Description
- 07/25 Code freeze for the endgame
- 07/29 Endgame done
- 08/04 Expected release date (this may change)
Monday
- Check that all queries in this issue use the current milestone @bpasero
- Run OSS tool @bpasero
- Update links in the Endgame notebooks to point to new milestone @bpasero
- 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-neededoron-testplanlabel - Create test plan items following the template here by 6pm PT
- Update your availability for testing here - https://vscode-tools.azurewebsites.net/team-manifest team
- Update availability of testers in vacation. Double check N/A testers. @bpasero
Tuesday
- Test plan items assigned (using https://vscode-tools.azurewebsites.net/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, 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
- 🔖Verification needed
- 🔖Verification
Friday
- Build a
stablebuild to ensure stable build is green @bpasero - Pause scheduled
insiderbuilds @bpasero - Satellite modules/npm packages ready, version updated, smoke tested
- yo generator @aeschli
- js-debug @connor4312
- debug adapter protocol @connor4312
- node debugadapter node @connor4312
- mock debug @connor4312
- custom data for html/css @aeschli
- Only candidate issues are open and assigned to 🔖milestone
- All issues 🔖verified
- All open PRs on the milestone 🔖merged or deferred
- Branch code to
release/<x.y>after all expected fixes are in (latest 5PM PST) @bpasero - Branch distro to
release/<x.y>after all expected fixes are in (latest 5PM PST) @bpasero - Announce
mainis open for business @bpasero - 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>.mdin this repo directory - @aeschli
- @alexdima
- @alexr00
- @andreamah
- @aiday-mar
- @benibenj
- @bpasero
- @chrmarti
- @connor4312
- @dbaeumer
- @deepak1556
- @egamma
- @hediet
- @isidorn
- @JacksonKearl
- @joaomoreno
- @joyceerhl
- @jrieken
- @kieferrm
- @lramos15
- @lszomoru
- @meganrogge
- @mjbvz
- @rebornix
- @roblourens
- @rzhao271
- @sandy081
- @sbatten
- @tanhakabir
- @TylerLeonhardt
- @Tyriar
- @weinand
- release notes are collected in a file named
- Acknowledge pull requests in release notes. We acknowledge PRs from outside the team. We have improved the tooling so that the endgame champion can generate the pull request acknowledgment for all repositories at once. @bpasero
-
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
- 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
- Build and manually release Insider from release/<x.y> @bpasero
- Localization: Run Update VS Code Branch in the vscode-loc-drop repo with
release/*as the VS Code Branch parameter (it's the default so you shouldn't have to change anything) @TylerLeonhardt
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>@bpasero - Build
Insiderfromrelease/<x.y>@bpasero - Manually release
Insider@bpasero - Build stable for all platforms as new candidate issues come in @bpasero
- Documentation updated
- @aeschli
- @alexdima
- @alexr00
- @andreamah
- @aiday-mar
- @benibenj
- @bpasero
- @chrmarti
- @connor4312
- @dbaeumer
- @deepak1556
- @egamma
- @hediet
- @isidorn
- @JacksonKearl
- @joaomoreno
- @joyceerhl
- @jrieken
- @kieferrm
- @lramos15
- @lszomoru
- @meganrogge
- @mjbvz
- @rebornix
- @roblourens
- @rzhao271
- @sandy081
- @sbatten
- @TylerLeonhardt
- @Tyriar
- @weinand
- Run
scripts/test-documentation.sh|batand add file or fix issues if there are new colors that are not documented. @bpasero
Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame. @bpasero
Wednesday/Thursday - Expected release day (this may change)
- Build stable for all platforms @bpasero
- Sanity check of installable bits (server instructions)
- Windows 32 bit owner
- signed installer 32-bit
- signed user installer 32-bit
- zip 32-bit
- server 32-bit
- Windows 64 bit owner
- signed installer 64-bit
- signed user installer 64-bit
- zip 64-bit
- server 64-bit
- Windows ARM64 owner
- signed installer ARM64
- signed user installer ARM64
- zip ARM64
- macOS
- Universal owner
- Intel owner
- Intel server owner
- Apple Silicon owner
- Linux x64
- deb owner
- rpm owner
- archives owner
- snap (
sudo snap install --classic --dangerous <file>.snap) owner
- Linux server owner
- x64
- x64 Alpine
- ARM32
- ARM64
- Windows 32 bit owner
- Publish website @gregvanl
- Publish to stable @bpasero
- Trigger the vscode.dev Deploy pipeline for the
proddeployment target. Request approval from another team member at the necessary step. @bpasero - Create an official release @bpasero
- 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
- Create a tag (make sure you pull the release branch first):
- Twitter announcement @chrisdias
- Enable scheduled
insiderbuilds @bpasero - Bump up the version in
package.jsononmain- @bpasero - Publish @types/vscode @bpasero
- Close the milestone on GitHub @bpasero
- 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 @bpasero
- If no Patch Tuesday release is planned, let the Updates team know of that fact (CSEClientPatching@microsoft.com) @bpasero
- 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/ @bpasero