Closed
Description
- September 28 Code freeze for the endgame
- October 2 Endgame done
- October 7 Expected release date (this may change)
Monday
- Run OSS tool @bpasero
- 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) @bpasero
Tuesday
- Test plan items assigned (using https://vscode-tools.azurewebsites.net/) @bpasero
- 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-neededoron-testplanlabel - 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-testand fixed @bpasero
Thursday
- Fixing (self-assigned, milestone assigned, NO discussion during standup)
- Move issues to the next month that can be deferred
- 🔖Verification needed
- 🔖Verification
- Prepare for Smoke test: Make sure all smoke test issues are labelled
smoke-testand fixed @bpasero
Friday
- Pause scheduled
insiderbuilds @bpasero - 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-buildargument⚠️ ) - All release notes updated
- release notes are collected in a file named
v<Major>_<Minor>.mdin 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
- @rzhao271
- @meganrogge
- release notes are collected in a file named
- 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 @bpasero
- 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 @weinand
- localization @weeteckt
- vscode-github-issues-prs @chrmarti
- inno-updater @joaomoreno
- Review pull requests acknowledgements with
NOT MERGED - PLS REVIEW. @bpasero - 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 @bpasero
- Branch code to `release/<x.y> @bpasero
- Bump up the version in package.json - @bpasero
- Announce master is open for business @bpasero
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
- Run
scripts/test-documentation.sh|batand add file or fix issues if there are new colors that are not documented.
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
- Windows 32 bit @dbaeumer
- signed installer 32-bit
- signed user installer 32-bit
- zip 32-bit
- Windows 64 bit @alexr00
- signed installer 64-bit
- signed user installer 64-bit
- zip 64-bit
- Windows ARM64 @joaomoreno
- signed installer ARM64
- signed user installer ARM64
- zip ARM64
- macOS - @bpasero
- Linux @bpasero
- deb package 64-bit owner
- rpm package 64-bit owner
- archives owner
- snap (
sudo snap install --classic --dangerous <file>.snap) owner
- Server (instructions) owner
- Windows 32 bit @dbaeumer
- Publish website @ornellaalt
- Publish Localization language pack @weeteckt
- Publish to stable @JacksonKearl
- Create an official release @JacksonKearl
- 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
- Create a tag:
- Publish @types/vscode @bpasero
- Enable scheduled
insiderbuilds @JacksonKearl - Twitter announcement @chrisdias