March 2019 Endgame

[weinand]

This is the endgame schedule for March 2019 Iteration.

Schedule

• End game master: @weinand / Zurich
• End game buddy: @octref / Redmond
• 03/25 Code freeze for the endgame
• 03/29 Endgame done
• 04/04 Expected release date (this may change)

Note: The Insiders build 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 @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 @isidorn for verification @weinand

Friday 03/29

• Pause scheduled insider builds @weinand
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno
  • node debug @weinand
  • node debug2 @roblourens
  • node debugadapter node @weinand
  • debug-adapter-protocol @weinand
• All issues verified
• Fixing (only critical bugs - no string changes)
• Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
  • Windows - @dbaeumer
  • OS X - @alexandrudima
  • Linux - @aeschli
• All release notes updated
  • release notes are collected in a file named Month_Year.md in 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⚠️
  • @aeschli
  • @alexandrudima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @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. owner
  • vscode @weinand
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-debugadapter-node @weinand
  • debug-adapter-protocol @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 @shawndon
  • vscode-github-issues-prs @chrmarti
  • inno-updater @joaomoreno
• Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. @weinand
• 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 @weinand

Friday/Monday

• Branch code to `release/<x.y> @weinand
• Bump up the version in package.json - @weinand
• Announce master is open for business @weinand
• Polish release notes redmond

Monday - Wednesday

• Polish release notes redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @weinand
• Build Insider from release/<x.y> @weinand
• Manually release Insider @weinand
• Build stable for all platforms as new candidate issues come in @weinand
• Documentation updated
  • @aeschli
  • @alexandrudima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @sbatten
  • @Tyriar
  • @weinand

Note: The Insiders build 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 @weinand
• Make rpm signing request @RMacfarlane
• Sanity check of installable bits
  • Windows
    • signed installer 32-bit @roblourens
    • signed installer 64-bit @octref
    • signed user installer 32-bit @roblourens
    • signed user installer 64-bit @octref
    • zip 32-bit @roblourens
    • zip 64-bit @octref
  • OS X - @octref
  • Linux
    • deb package 32-bit @RMacfarlane
    • deb package 64-bit @sbatten
    • rpm package 64-bit @RMacfarlane
    • rpm package 32-bit @RMacfarlane
    • archive 32-bit @RMacfarlane
    • archive 64-bit @RMacfarlane
• Publish website @gregvanl
• Publish Localization language pack @shawndon
• Publish to stable @weinand
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @weinand
• Publish @types/vscode@<x.y> @octref
• Publish rpm to repository manually @RMacfarlane
• Enable scheduled insider builds @weinand
• Twitter announcement @auchenberg

[dzienisz]

What is happening with the last two releases, both were delayed?

[weinand]

@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).

04/04 Expected release date (this may change)

[weinand]

March released shipped!

[dzienisz]

@weinand thanks for the answer!