January 2018 Endgame

[ramya-rao-a]

EndGame Schedule

• January 29th Code freeze for the endgame
• February 2nd 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

• 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

• Test plan items assigned
• All closed feature-requests either have a verification-needed or on-testplan tag
• Test build starts at 7am CET / 10pm PT on Monday
• Test plan ready by 8am CET / 11pm PT on Monday
• Testing

Wednesday

• Complete Testing
• Verify features that need verfification
• Remind team members to assign issues that they intend to fix to the current milestone
• Fixing bugs (self-assigned, milestone assigned)
• Bug Verification

Thursday

• Fixing major bugs (scrutiny sets in - major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• Bug Verification and features that need verfification
• Start updating release notes
  • release notes are collected in a file named Major_Minor.md in this repo directory
• Run OSS tool after merge output @ramya-rao-a
• Check new OSS usage is entered into the OSS registry @ramya-rao-a

Friday

• Pause scheduled insider builds @kieferrm
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno
  • node debug @weinand
  • node debug2 @roblourens
  • node debugadapter @weinand
• All issues verified
• Fixing (only critical bugs - no string changes, major bugs only - to be discussed in stand-up meeting, labeled as candidate)
• Smoketest
  • Windows - @dbaeumer
  • OS X - @bpasero
  • Linux - @joaomoreno
• All release notes updated with features and notable fixes
  • @alexandrudima
  • @weinand
  • @bpasero
  • @chrmarti
  • @Tyriar
  • @dbaeumer
  • @egamma
  • @isidorn
  • @jrieken
  • @joaomoreno
  • @kieferrm
  • @aeschli
  • @mjbvz
  • @rebornix
  • @octref
  • @RMacfarlane
  • @ramya-rao-a
  • @roblourens
  • @sandy081
• 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.
  • vscode endgame master
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-debugadapter-node @weinand
  • 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 @chrisdias
  • vscode-tslint @egamma
  • vscode-eslint @dbaeumer
  • vscode-jshint @RMacfarlane
  • vscode-recipes @auchenberg
  • localization @danyeh
  • vscode-github-issues-prs @chrmarti
• When done fixing/verifying and there are changes since last build at the end of day PT
  • Trigger new insider build @ramya-rao-a
  • and publish it manually @kieferrm

Friday/Monday

• Branch code to `release/<x.y> @alexandrudima
• Announce master is open for business @alexandrudima
• 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 @alexandrudima
• Polish release notes @redmond

Monday - Wednesday

• Polish release notes @redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @ramya-rao-a, @ alexandrudima
• Build Insider from release/<x.y> @@ramya-rao-a
• Manually release Insider @kieferrm
• Another round of Smoketest
  • Windows - @ramya-rao-a
  • OS X - @roblourens
  • Linux - @RMacfarlane
• Merge the translation pull request into the release/<x.y> and master branch @dbaeumer
• Documentation updated
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @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.

Thursday/Friday

• Check translations (check i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @zurich
• Build stable for all platforms @ramya-rao-a/@alexandrudima
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @ramya-rao-a/@alexandrudima
• new Make sure that the vsda module version in stable is the same as in insiders (which matches the latest electron) @ramya-rao-a/@alexandrudima
• Make rpm signing request @Tyriar
• Sanity check of installable bits
  • Windows
    • signed installer 32-bit @ramya-rao-a
    • signed installer 64-bit @roblourens
    • zip 32-bit @mjbvz
    • zip 64-bit @roblourens
  • OS X - @octref
  • Linux
    • deb package 32-bit @RMacfarlane
    • deb package 64-bit @RMacfarlane
    • rpm package 64-bit @Tyriar
    • rpm package 32-bit @Tyriar
    • archives @rebornix
• Publish website @gregvanl
• Publish to stable @Tyriar
• Publish deb and rpms to repositories manually @Tyriar
• Add version with symbols to HockeyApp @Tyriar
• Enable scheduled insider builds @Tyriar
• Twitter announcement @auchenberg

Recovery Build

Day 1 (2/13)

• Create a milestone <Month> Recovery <year> @ramya-rao-a
• Include an issue 'update translations' @ramya-rao-a
• 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 stable build from master
• Issues are verified on stable build and the verified label is added @team
• Smoketest stable bits
  • Windows - @mjbvz
  • OS X - @octref
  • Linux - @rebornix
• Make rpm signing request @Tyriar

Day 2 (2/14)

• Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @sandy081
• Sanity check installable stable bits that have not been smoke tested
  • Windows @alexandrudima
    • signed installer 32-bit @zurich
    • signed installer 64-bit @zurich
    • zip 32-bit @zurich
    • zip 64-bit @zurich
  • OS X - @weinand
  • Linux
    • deb package 32-bit @aeschli
    • deb package 64-bit @chrmarti
    • rpm package 64-bit @aeschli
    • rpm package 32-bit @chrmarti
    • archives @aeschli
• Update the release notes and include a link to a query for the fixed issues @gregvanl
• Publish website @egamma
• Publish stable build @egamma
• Publish deb and rpms to repositories manually @chrmarti
• Add a git tag to HEAD of release/<x.y> in format x.y.z @joaomoreno