August Endgame

[bpasero]

August 27th: Code freeze for the endgame
August 31th: 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

• Run OSS tool @bpasero
  • 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 sufficiently comprehensive test descriptions by 6pm PT
• Update your availability for testing here - https://vscode-tools.azurewebsites.net/

Tuesday

• Test plan items assigned @bpasero
• 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

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

Thursday

• Fixing (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• Verification needed
• Verification
• Check new OSS usage is entered into the OSS registry @bpasero

Friday

• Pause scheduled insider builds @bpasero

• 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

• All issues verified

• Fixing (only critical bugs)

• Smoketest

  • Windows - @dbaeumer
  • OS X - @alexandrudima
  • Linux - @sandy081

• All release notes updated

  • release notes are collected in a file named v1_27.md in this repo directory
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @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 @bpasero
  • 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 @danyeh
  • vscode-github-issues-prs @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 @bpasero

  Friday/Monday

• Redmond: Labor day on Monday

• Branch code to `release/<x.y> @bpasero

• Bump up the version in package.json - @bpasero

• Announce master is open for business @bpasero

• Let Daniel Ye know that the release branch release/<x.y> got created and that translation should be pulled from there and that the pull request has to be created against that branch @bpasero

• Polish release notes redmond

Monday - Wednesday

• Polish release notes redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @bpasero
• Build Insider from release/<x.y> @bpasero
• Manually release Insider @bpasero
• Documentation updated
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @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 @bpasero
• Make rpm signing request @Tyriar
• Sanity check of installable bits
  • Windows
    • signed installer 32-bit @bpasero
    • signed installer 64-bit @bpasero
    • signed user installer 32-bit @bpasero
    • signed user installer 64-bit @bpasero
    • zip 32-bit @bpasero
    • zip 64-bit @bpasero
  • OS X - @bpasero
  • Linux
    • deb package 32-bit owner
    • deb package 64-bit @bpasero
    • rpm package 64-bit owner
    • rpm package 32-bit owner
    • archives owner
• Publish website @gregvanl
• Publish to stable @octref
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @octref
• Publish deb and rpms to repositories manually @Tyriar
• Enable scheduled insider builds @octref
• Twitter announcement @seanmcbreen

[endgame]

Am I going to get subscribed to one of these every month? =/

[chpxu]

Since they @ you, probably :P

[chrmarti]

@owner is in the same boat. ^^

[bpasero]

Sorry, will not happen again.

[oneslash]

Acknowledge pull requests in release notes - so is not vscode-go, not the first-class citizen?

maybe you can write something like @#_ms-endgame instead only "@engame"

prefixes are solving all.

[jens1o]

Will the release be delayed?

[egamma]

@jens1o why do you think the release is delayed? We always ship the week after the endgame (pls see inside an iteration).

[egamma]

@oneslash vscode-go is an important extension. It is driven by a broad community and this extension acknowledges contributions in the Change Log of the extension.

[jens1o]

@egamma Well, you want to ship tomorrow, but there are many checkboxes(tasks) that are not done, yet.

[egamma]

@jens1o I appreciate that you track our progress, but you are off-by-one week 😎 .

The endgame is done August 31 and we ship the week after the endgame. From inside an iteration: