May Endgame

[RMacfarlane]

Endgame Schedule

• May 28th, Code freeze for the endgame
• June 1, 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.

Friday

Note: Monday is a holiday for the Redmond team

• Redmond code freeze a 5pm PT
• Ensure build is green on all platforms at 5pm PT
• All Redmond team members have submitted test items

Monday

• Code freeze at 5pm PT
• Ensure we have a green build on all platforms at 5pm PT
• All test items are created (with "complexity" but not necessarily with full description) by 5pm PT
• All test items contain comprehensive test descriptions by 6pm PT
• Update your availability for testing here - https://vscode-tools.azurewebsites.net/

Tuesday

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

Wednesday

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

Thursday & Friday

• Fixing last issues
• Verification needed
• Verification
• Satellite modules/npm packages ready, version updated, smoke tested
  • vscode @bpasero
  • yo generator @aeschli
  • vsce @joaomoreno
  • node-debugadapter-node @weinand
  • node-debug @weinand
  • node-debug2 @roblourens
• Check translations (check i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @dbaeumer
• All release notes updated - release notes are collected in a file named v1_24.md in this repo directory. This includes new features and notable fixes.
  • @aeschli
  • @alexandrudima
  • @bpasero
  • @chrmarti
  • @dbaeumer
  • @egamma
  • @isidorn
  • @joaomoreno
  • @jrieken
  • @kieferrm
  • @mjbvz
  • @octref
  • @ramya-rao-a
  • @rebornix
  • @RMacfarlane
  • @roblourens
  • @sandy081
  • @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:
  • vscode endgame master
  • vscode-node-debug @weinand
  • vscode-node-debug2 @roblourens
  • vscode-debugadapter-node @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
  • vscode-azure-account @chrmarti
  • vscode-azurecli @chrmarti
• Run OSS tool endgame master
  • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • do not forget to update the distro attribute in the package.json with the commit ID of the distro repo.
  • Create list for team members to enter new OSS usage into the OSS registry endgame master
• Register new components in OSS registry
• Fixing (only critical bugs - no string changes)
• Smoketest
  • Windows
  • OS X
  • Linux
• 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 change author
• Disable continuous insider builds - endgame master
• Branch code to release/<x.y> - endgame master
• Bump up the version in package.json in master - endgame master
• Announce master is open for business endgame master

Friday / Monday week 2

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

Monday/Tuesday week 2

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

Wednesday/Thursday week 2

• Merge translations PR (if it makes it in time) endgame master
• Build stable for all platforms endgame master
• Make rpm signing request @RMacfarlane
• Sanity check of installable bits
  • Windows
    • signed installer @owner
    • zip @owner
  • OS X - @owner
  • Linux
    • deb package 64-bit @owner
    • deb package 32-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 @RMacfarlane
• 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