March 2019 Endgame #71059
Copy link
Copy link
Closed
Labels
endgame-planVS Code - Next release plan for endgameVS Code - Next release plan for endgame
Milestone
Description
This is the endgame schedule for March 2019 Iteration.
Schedule
- End game master: Andre Weinand (@weinand) / Zurich
- End game buddy: Pine (@octref) / Redmond
- 03/25 Code freeze for the endgame
- 03/29 Endgame done
- 04/04 Expected release date (this may change)
Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
Monday 03/25
- Run OSS tool Andre Weinand (@weinand)
- The LCA review of the ThirdPartyNotices.txt files is not needed anymore
- Code freeze at 5pm PT
- Ensure we have a green build on all platforms at 5pm PT
- All test items contain test meta data by 5pm PT and sufficiently comprehensive test descriptions by 8am CET
- Update your availability for testing here - https://vscode-tools.azurewebsites.net/
Tuesday 03/26
- Test plan items assigned (using https://vscode-tools.azurewebsites.net/)
- Run the tool multiple times to balance load if test items come in later and assignments are already made
- All closed feature-requests either have a verification-needed or on-testplan tag
- Test build starts at 7am CET
- Test plan ready by 8am CET
- Testing
- Verification needed
Wednesday 03/27
- Testing
- Remind team members to assign issues that they intend to fix to the current milestone
- Fixing (self-assigned, milestone assigned)
- Verification
Thursday 03/28
- Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as
candidate) - Verification
- Run OSS tool and pass list of changed OSS usage (https://github.com/Microsoft/vscode-build-tools/blob/master/distro-tools/license/third_party_1.nn.0_diff.txt) to Isidor Nikolic (@isidorn) for verification Andre Weinand (@weinand)
Friday 03/29
- Pause scheduled
insiderbuilds Andre Weinand (@weinand) - Satellite modules/npm packages ready, version updated, smoke tested
- vscode Benjamin Pasero (@bpasero)
- yo generator Martin Aeschlimann (@aeschli)
- vsce João Moreno (@joaomoreno)
- node debug Andre Weinand (@weinand)
- node debug2 roblourens
- node debugadapter node Andre Weinand (@weinand)
- debug-adapter-protocol Andre Weinand (@weinand)
- All issues verified
- Fixing (only critical bugs - no string changes)
- Smoketest (
⚠️ MUST run with--stable-buildargument⚠️ )- Windows - Dirk Bäumer (@dbaeumer)
- OS X - alexandrudima
- Linux - Martin Aeschlimann (@aeschli)
- All release notes updated
- release notes are collected in a file named
Month_Year.mdin this repo directory.⚠️ We are now doing release notes via Git LFS. Please read what this means here: https://github.com/Microsoft/vscode-docs/blob/vnext/README.md#git-lfs-setup⚠️ - Martin Aeschlimann (@aeschli)
- alexandrudima
- Alex Ross (@alexr00)
- 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)
- Peng Lyu (@rebornix)
- Rachel Macfarlane (@RMacfarlane)
- roblourens
- Sandeep Somavarapu (@sandy081)
- SteVen Batten (@sbatten)
- Daniel Imms (@Tyriar)
- Andre Weinand (@weinand)
- 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 Andre Weinand (@weinand)
- vscode-node-debug Andre Weinand (@weinand)
- vscode-node-debug2 roblourens
- vscode-debugadapter-node Andre Weinand (@weinand)
- debug-adapter-protocol 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 R. Shawn Donat (@shawndon)
- vscode-github-issues-prs Christof Marti (@chrmarti)
- inno-updater João Moreno (@joaomoreno)
- Review pull requests acknowledgements with
NOT MERGED - PLS REVIEW. Andre Weinand (@weinand) - Acknowledge issue trackers from the community Christof Marti (@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 Andre Weinand (@weinand)
Friday/Monday
- Branch code to `release/<x.y> Andre Weinand (@weinand)
- Bump up the version in package.json - Andre Weinand (@weinand)
- Announce master is open for business Andre Weinand (@weinand)
- Polish release notes redmond
Monday - Wednesday
- Polish release notes redmond
- Cherry-pick hand-picked and reviewed changes to
release/<x.y>Andre Weinand (@weinand) - Build
Insiderfromrelease/<x.y>Andre Weinand (@weinand) - Manually release
InsiderAndre Weinand (@weinand) - Build stable for all platforms as new candidate issues come in Andre Weinand (@weinand)
- Documentation updated
- Martin Aeschlimann (@aeschli)
- alexandrudima
- Alex Ross (@alexr00)
- 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)
- Peng Lyu (@rebornix)
- Rachel Macfarlane (@RMacfarlane)
- roblourens
- Sandeep Somavarapu (@sandy081)
- SteVen Batten (@sbatten)
- Daniel Imms (@Tyriar)
- Andre Weinand (@weinand)
Note: The
Insidersbuild needs to be in the wild for 24 hours before we can enter the last phase of the endgame.
Wednesday/Thursday
- Build stable for all platforms Andre Weinand (@weinand)
- Make rpm signing request Rachel Macfarlane (@RMacfarlane)
- Sanity check of installable bits
- Windows
- signed installer 32-bit roblourens
- signed installer 64-bit Pine (@octref)
- signed user installer 32-bit roblourens
- signed user installer 64-bit Pine (@octref)
- zip 32-bit roblourens
- zip 64-bit Pine (@octref)
- OS X - Pine (@octref)
- Linux
- deb package 32-bit Rachel Macfarlane (@RMacfarlane)
- deb package 64-bit SteVen Batten (@sbatten)
- rpm package 64-bit Rachel Macfarlane (@RMacfarlane)
- rpm package 32-bit Rachel Macfarlane (@RMacfarlane)
- archive 32-bit Rachel Macfarlane (@RMacfarlane)
- archive 64-bit Rachel Macfarlane (@RMacfarlane)
- Windows
- Publish website Greg Van Liew (@gregvanl)
- Publish Localization language pack R. Shawn Donat (@shawndon)
- Publish to stable Andre Weinand (@weinand)
- Add a git tag to
HEADofrelease/<x.y>in formatx.y.z(for vscode.d.ts download) Andre Weinand (@weinand) - Publish
@types/vscode@<x.y>Pine (@octref) - Publish rpm to repository manually Rachel Macfarlane (@RMacfarlane)
- Enable scheduled
insiderbuilds Andre Weinand (@weinand) - Twitter announcement Kenneth Auchenberg (@auchenberg)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
endgame-planVS Code - Next release plan for endgameVS Code - Next release plan for endgame
Activity
dzienisz commentedon Apr 4, 2019
What is happening with the last two releases, both were delayed?
weinand commentedon Apr 4, 2019
Kamil Dzieniszewski (@dzienisz) no, we are always shipping the release in the week after the endgame.
You can always find the expected release date in the first comment of the endgame (above).
weinand commentedon Apr 4, 2019
March released shipped!
dzienisz commentedon Apr 5, 2019
Andre Weinand (@weinand) thanks for the answer!