May 2019 Endgame

[aeschli]

This is the endgame schedule for May 2019 Iteration.

Schedule

• End game master: @rebornix / Redmond
• End game buddy: @aeschli / Zurich
• 05/28 Code freeze for the endgame
• 05/31 Endgame done
• 06/06 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.

Tuesday 05/28

• Run OSS tool @aeschli
  • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
• Code freeze at 5pm CET
• Ensure we have a green build on all platforms at 5pm CET
• All test items contain test meta data by 5pm CET and sufficiently comprehensive test descriptions by 8am CET
• Update your availability for testing here - https://vscode-tools.azurewebsites.net/
• 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
• Test build starts at 6pm CET
• Test plan ready by 6pm CET
• Testing
• All closed feature-requests either have a verification-needed or on-testplan tag
• Verification needed
• Verification needed for Remote

Wednesday

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

Thursday

• Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)

• Verification

• All issues verified

• 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 @rebornix

• 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

• Fixing (only critical bugs - no string changes)

• Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )

  • Windows
  • OS X
  • Linux

• 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
  • @deepak1556
  • @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 @aeschli
  • 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. @aeschli

• 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 @aeschli

Friday/Monday

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

Monday - Wednesday

• Polish release notes redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @rebornix
• Build Insider from release/<x.y> @rebornix
• Manually release Insider @rebornix
• Build stable for all platforms as new candidate issues come in @rebornix
• Documentation updated
  • @aeschli
  • @alexandrudima
  • @alexr00
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @deepak1556
  • @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 @rebornix
• Make rpm signing request @RMacfarlane
• Sanity check of installable bits
  • Windows
    • signed installer 32-bit
    • signed installer 64-bit @sbatten
    • signed user installer 32-bit
    • signed user installer 64-bit @sbatten
    • zip 32-bit
    • zip 64-bit @sbatten
  • OS X
  • Linux
    • deb package 32-bit
    • deb package 64-bit
    • rpm package 64-bit @RMacfarlane
    • rpm package 32-bit @RMacfarlane
    • archive 32-bit @RMacfarlane
    • archive 64-bit
• Publish website @gregvanl
• Publish Localization language pack @shawndon
• Publish to stable @rebornix
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @rebornix
• Publish @types/vscode@<x.y> @rebornix
• Publish rpm to repository manually @RMacfarlane
• Enable scheduled insider builds @rebornix
• Twitter announcement @auchenberg

[gjsjohnmurray]

Can this be pinned, i.e. so it appears at the top of Issues? maybe the Iteration Plan (#74143) too? That has been done on previous iterations.

[tristan957]

Do the iteration plans typically lag VSCode releases? 1.35 is available on the website, but hasn't been updated in the DNF repo (Fedora).

[lig]

@tristan957 I guess, this line in the plan is somewhat relevant

Publish rpm to repository manually @RMacfarlane 

[Tyriar]

@tristan957 @lig we're still waiting on the signing to be completed, it will probably be published today.

[tristan957]

Did the update get published? I see from the checklist that the signing got completed.

[Tyriar]

We're still waiting on the signing unfortunately, hopefully Monday.

[RMacfarlane]

@tristan957 The rpm is now published.

[rebornix]

May release is out and closed in favor of #75285 .