June endgame

[roblourens]

Endgame Schedule

• June 26, Code freeze for the endgame
• July 7, Endgame done

Monday, June 26

• Code freeze at 5pm PT
• Ensure we have a green build on all platforms
• All test items contain sufficiently comprehensive test descriptions by 6pm PT

Tuesday, June 27

• Test plan items assigned
• All closed feature-requests either have a verification-needed or on-testplan tag
• Testing
• Verification needed

Wednesday, June 28

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

Thursday, June 29

• Fixing last issues
• Verification
• Run OSS tool after merging shrink-wrap findings endgame master
  • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
• Check new OSS usage is entered into the OSS registry endgame master

Friday, June 30

• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @dbaeumer
  • vsce @joaomoreno
  • node debug @weinand
  • node debug2 @roblourens
• Check translations (build locally and see the amount of untranslated strings) @michelkaporin
• All issues verified
• Fixing (only critical bugs - no string changes)
• Smoketest
  • Windows - @egamma
  • OS X - @sandy081
  • Linux - @joaomoreno
• All release notes updated - release notes are collected in a file named Month_Year.md in this repo directory. This includes new features and notable fixes.
  • @alexandrudima
  • @weinand
  • @chrmarti
  • @Tyriar
  • @dbaeumer
  • @bpasero
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @aeschli
  • @rebornix
  • @ramya-rao-a
  • @roblourens
  • @sandy081
  • @mjbvz
  • @michelkaporin
• 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 endgame master
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-filewatcher-windows @bpasero
  • 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 @cdias
  • vscode-tslint @egamma
  • vscode-eslint @dbaeumer
  • vscode-jshint @kieferrm
  • localization @danyeh @michelkaporin
• 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 @owner

Friday/Monday

• Disable continuous insider builds - endgame master
• Branch code to release/<x.y> and release master - endgame master
• Bump up the version in package.json - endgame master
• Announce master is open for business endgame master
• Polish release notes @redmond

Tuesday, July 4 - Redmond holiday

• Fireworks
• Grill stuff

Monday - Wednesday

• Polish release notes @redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @owner
• Build Insider from release/<x.y> endgame master
• Manually release Insider endgame master
• Documentation updated
  • @alexandrudima
  • @weinand
  • @chrmarti
  • @Tyriar
  • @dbaeumer
  • @bpasero
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @aeschli
  • @rebornix
  • @ramya-rao-a
  • @roblourens
  • @sandy081
  • @mjbvz

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Thursday/Friday

• Merge translations @zurich
• Build stable for all platforms endgame master
• Make rpm signing request @Tyriar
• Sanity check of installable bits
  • Windows
    • signed installer @owner
    • zip @owner
  • OS X - @owner
  • Linux
    • deb package 32-bit @owner
    • deb package 64-bit @owner
    • rpm package 64-bit @owner
    • rpm package 32-bit @owner
    • archives @owner
• Publish website @gregvanl
• Publish to stable @owner
• Publish deb and rpms to repositories manually @Tyriar
• Add version with symbols to HockeyApp @bpasero
• Add a git tag to HEAD of release/<x.y> in format x.y.z endgame master
• Enable scheduled insider builds endgame master
• Twitter announcement @seanmcbreen

[roblourens]

• Wed pm Redmond: build, validate issues are resolved, smoke test
• Redmond: Publish insiders with new TS
• Thu am Zurich: pick up latest bits, validate, smoke test
• Thu am Redmond: Sync with Zurich, see if any new issue arise
• Thu pm Redmond: ship 1.14.2

Release checklist

• Create a milestone <Month> Recovery <year> @owner
• Include an issue 'update translations' @owner
• Assign candidate issues to the recovery milestone @team
• Review the candidate issues, and if they pass the review assign them to the recovery milestone @team
• All candiate fixes are peer reviewed and pushed to master and then cherry-picked into the release branch @team
• Initiate insiders build from master
• Issues are tested in the insiders @team
• Build stable for all platforms from release branch @owner
• Make rpm signing request @Tyriar
• Issues are verified on stable build and the verified label is added @owner
• Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @owner
• Update the release notes and include a link to a query for the fixed issues @gregvanl
• Smoketest stable bits
  • Windows - @owner
  • OS X - @owner
  • Linux - @owner
• Sanity check installable stable bits that have not been smoke tested
  • Windows
    • signed installer 32-bit @owner
    • signed installer 64-bit @owner
    • zip 32-bit @owner
    • zip 64-bit @owner
  • OS X - @owner
  • Linux
    • deb package 32-bit @owner
    • deb package 64-bit @owner
    • rpm package 64-bit @owner
    • rpm package 32-bit @owner
    • archives @owner
• Publish website @gregvanl
• Publish stable build @owner
• Publish deb and rpms to repositories manually @Tyriar
• Add a git tag to HEAD of release/<x.y> in format x.y.z

[joaomoreno]

@roblourens Should this be closed?