Repository navigation
March Endgame #46620
Description
Endgame Schedule
- March 26th, Code freeze for the endgame
- March 30th, Endgame done
Note: The
Insidersbuild 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 Benjamin Pasero (@bpasero)
- yo generator Martin Aeschlimann (@aeschli)
- vsce Sandeep Somavarapu (@sandy081)
- node-debugadapter-node Andre Weinand (@weinand)
- node-debug Andre Weinand (@weinand)
- node-debug2 roblourens
- Check translations (check
i18nfolder git history for latest translations, then build locally and see the amount of untranslated strings) Dirk Bäumer (@dbaeumer) - All release notes updated - release notes are collected in a file named
v1_22.mdin this repo directory. This includes new features and notable fixes.- Martin Aeschlimann (@aeschli)
- alexandrudima
- Benjamin Pasero (@bpasero)
- Christof Marti (@chrmarti)
- Dirk Bäumer (@dbaeumer)
- Erich Gamma (@egamma)
- Isidor Nikolic (@isidorn)
- João Moreno (@joaomoreno)
- Johannes Rieken (@jrieken)
- Kai Maetzel (@kieferrm)
- Matt Bierner (@mjbvz)
- Pine (@octref)
- Ramya Rao (@ramya-rao-a)
- Peng Lyu (@rebornix)
- Rachel Macfarlane (@RMacfarlane)
- roblourens
- Sandeep Somavarapu (@sandy081)
- Daniel Imms (@Tyriar)
- Andre Weinand (@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 Andre Weinand (@weinand)
- vscode-node-debug2 roblourens
- vscode-debugadapter-node Andre Weinand (@weinand)
- vscode-languageserver-node Dirk Bäumer (@dbaeumer)
- language-server-protocol Dirk Bäumer (@dbaeumer)
- vscode-textmate alexandrudima
- vscode-loader alexandrudima
- vscode-generator-code Martin Aeschlimann (@aeschli)
- vscode-vsce João Moreno (@joaomoreno)
- vscode-docs Greg Van Liew (@gregvanl)
- vscode-css-languageservice Martin Aeschlimann (@aeschli)
- vscode-json-languageservice Martin Aeschlimann (@aeschli)
- vscode-html-languageservice Martin Aeschlimann (@aeschli)
- jsonc-parser Martin Aeschlimann (@aeschli)
- vscode-jscs Chris Dias (@chrisdias)
- vscode-tslint Erich Gamma (@egamma)
- vscode-eslint Dirk Bäumer (@dbaeumer)
- vscode-jshint Rachel Macfarlane (@RMacfarlane)
- vscode-recipes Kenneth Auchenberg (@auchenberg)
- localization Daniel Ye (@danyeh)
- vscode-github-issues-prs Christof Marti (@chrmarti)
- Run OSS tool endgame master
- The LCA review of the ThirdPartyNotices.txt files is not needed anymore
- do not forget to update the
distroattribute 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
insiderbuilds - endgame master - Branch code to
release/<x.y>and releasemaster- 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
insiderbuilds - endgame master - Branch code to
release/<x.y>and releasemaster- endgame master - Bump up the version in
package.json- endgame master - Announce master is open for business endgame master
- Disable continuous
- Polish release notes Greg Van Liew (@gregvanl)
Monday week 2 - Wednesday week 2
- Polish release notes Greg Van Liew (@gregvanl)
- Cherry-pick hand-picked and reviewed changes to
release/<x.y>change author - Build
Insiderfromrelease/<x.y>endgame master - Manually release
Insiderendgame master - Documentation updated
- Martin Aeschlimann (@aeschli)
- alexandrudima
- Benjamin Pasero (@bpasero)
- Christof Marti (@chrmarti)
- Dirk Bäumer (@dbaeumer)
- Erich Gamma (@egamma)
- Isidor Nikolic (@isidorn)
- João Moreno (@joaomoreno)
- Johannes Rieken (@jrieken)
- Kai Maetzel (@kieferrm)
- Matt Bierner (@mjbvz)
- Pine (@octref)
- Ramya Rao (@ramya-rao-a)
- Peng Lyu (@rebornix)
- Rachel Macfarlane (@RMacfarlane)
- roblourens
- Sandeep Somavarapu (@sandy081)
- Daniel Imms (@Tyriar)
- Andre Weinand (@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 Daniel Imms (@Tyriar)
- Sanity check of installable bits
- Windows
- signed installer Owner (@owner)
- zip Owner (@owner)
- OS X - Owner (@owner)
- Linux
- deb package 64-bit Owner (@owner)
- deb package 32-bit Owner (@owner)
- rpm package 64-bit Owner (@owner)
- rpm package 32-bit Owner (@owner)
- archives Owner (@owner)
- Windows
- Publish website Greg Van Liew (@gregvanl)
- Publish to stable Owner (@owner)
- Publish deb and rpms to repositories manually Daniel Imms (@Tyriar)
- Add a git tag to
HEADofrelease/<x.y>in formatx.y.zendgame master - Enable scheduled
insiderbuilds endgame master - Twitter announcement Sean McBreen (@seanmcbreen)
Activity
borekb commentedon Apr 4, 2018
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 commentedon Apr 4, 2018
Borek Bernard (@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 commentedon Apr 4, 2018
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 commentedon Apr 9, 2018
Borek Bernard (@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 Daniel Imms (@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 commentedon Apr 9, 2018
Closing 1.22 has shipped.
borekb commentedon Apr 9, 2018
Erich Gamma (@egamma) thanks for the explanation, makes perfect sense.