March Endgame

[sandy081]

Endgame Schedule

• March 26th, Code freeze for the endgame
• March 30th, Endgame done

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

Monday

• Code freeze at 5pm PT
• Ensure we have a green build on all platforms at 5pm PT
• All test items are created (with "complexity" but not necessarily with full description) by 5pm PT
• All test items contain comprehensive test descriptions by 10pm PT
• Update your availability for testing here - https://vscode-tools.azurewebsites.net/

Tuesday

• Test plan items assigned
• All closed feature-requests without either verification-needed or on-testplan tag
• Testing
• Verification needed

Wednesday

• Remind team members to assign issues that they intend to fix to the February milestone
• Testing
• Fixing (self-assigned, milestone assigned)
• Verification needed
• Verification

Thursday & Friday

• Fixing last issues
• Verification needed
• Verification
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @sandy081
  • node-debugadapter-node @weinand
  • node-debug @weinand
  • node-debug2 @roblourens
• Check translations (check i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @dbaeumer
• All release notes updated - release notes are collected in a file named v1_22.md in this repo directory. This includes new features and notable fixes.
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @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:
  • vscode endgame master
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-debugadapter-node @weinand
  • vscode-languageserver-node @dbaeumer
  • language-server-protocol @dbaeumer
  • vscode-textmate @alexandrudima
  • vscode-loader @alexandrudima
  • 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-jscs @chrisdias
  • vscode-tslint @egamma
  • vscode-eslint @dbaeumer
  • vscode-jshint @RMacfarlane
  • vscode-recipes @auchenberg
  • localization @danyeh
  • vscode-github-issues-prs @chrmarti
• Run OSS tool endgame master
  • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • do not forget to update the distro attribute in the package.json with the commit ID of the distro repo.
  • Create list for team members to enter new OSS usage into the OSS registry endgame master
• Register new components in OSS registry
• Fixing (only critical bugs - no string changes)
• Smoketest
  • Windows
  • OS X
  • Linux
• 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 change author
• Disable continuous insider builds - endgame master
• Branch code to release/<x.y> and release master - endgame master
• Bump up the version in package.json - endgame master
• Announce master is open for business endgame master

Monday week 2

• If not done on Friday
  • Disable continuous insider builds - endgame master
  • Branch code to release/<x.y> and release master - endgame master
  • Bump up the version in package.json - endgame master
  • Announce master is open for business endgame master
• Polish release notes @gregvanl

Monday week 2 - Wednesday week 2

• Polish release notes @gregvanl
• Cherry-pick hand-picked and reviewed changes to release/<x.y> change author
• Build Insider from release/<x.y> endgame master
• Manually release Insider endgame master
• Documentation updated
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @Tyriar
  • @weinand

Thursday/Friday week 2

• Merge translations PR (if it makes it in time) endgame master
• Build stable for all platforms endgame master
• Make rpm signing request @Tyriar
• Sanity check of installable bits
  • Windows
    • signed installer @owner
    • zip @owner
  • OS X - @owner
  • Linux
    • deb package 64-bit @owner
    • deb package 32-bit @owner
    • rpm package 64-bit @owner
    • rpm package 32-bit @owner
    • archives @owner
• Publish website @gregvanl
• Publish to stable @owner
• Publish deb and rpms to repositories manually @Tyriar
• Add a git tag to HEAD of release/<x.y> in format x.y.z endgame master
• Enable scheduled insider builds endgame master
• Twitter announcement @seanmcbreen

[borekb]

Out of curiosity, what does "Endgame done" date mean? I think that during the past few iterations, it has always been at the end of week 1 while the endgame always seems to be planned to last two weeks.

Awesome release documentation BTW :)

[Tyriar]

@borekb at the top it's referring to the team's test/verification week. The following week we refer to as debt week and we focus on technical debt reduction and fix any remaining issues with the build that pop up. More info here https://github.com/Microsoft/vscode/wiki/Development-Process#inside-an-iteration 😄

[borekb]

Hmm, that wiki also seems to assume a single-week endgame which I don't think I've ever seen :)

But overall, I could measure month's progress just by looking at the GitHub Milestone progress bar, it's extremely impressive how predictably you deliver VSCode in a relatively large and distributed team. 🙇

[egamma]

Hmm, that wiki also seems to assume a single-week endgame which I don't think I've ever seen :)

@borekb the endgame is one week and the 'Endgame Done' date refers when the engineering work for the release is done. This date is different from when we ship the release. As @Tyriar explains above, after 'Endgame done' we let the release sit. We freeze the insiders channel so that we all test the latest bits and watch for critical issues. We review the critical issues daily. If there is a critical fix we wait for another 24 hours. Therefore the release date is during the week after the endgame, but we never release on a Friday. I´ll update the wiki with more detail. Given this I cannot remember an endgame that lasted longer than a week 💪, but glad to see your interest into our planning!

[egamma]

Closing 1.22 has shipped.

[borekb]

@egamma thanks for the explanation, makes perfect sense.