June Endgame

[isidorn]

• June 25th: Code freeze for the endgame
• June 29th: Endgame done

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
• Verification needed
• Run OSS tool after merging shrink-wrap findings @isidorn
  • The LCA review of the ThirdPartyNotices.txt files is not needed anymore

Wednesday

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

Thursday

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

Friday

• Pause scheduled insider builds @isidorn
• 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 - no string changes)
• Smoketest
  • Windows - @alexandrudima
  • OS X - @isidorn
  • Linux - @chrmarti
• All release notes updated - release notes are collected in a file named v1_25.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. isidorn
  • 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
• 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 @isidorn

Friday/Monday

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

Monday - Wednesday

• Polish release notes @redmond
• Cherry-pick hand-picked and reviewed changes to release/<x.y> @isidorn
• Build Insider from release/<x.y> @isidorn
• Manually release Insider @isidorn
• 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 @isidorn
• Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @isidorn
• new Make sure that the vsda module version in stable is the same as in insiders (which matches the latest electron)
• Make rpm signing request @Tyriar
• Sanity check of installable bits
  • 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 to stable @isidorn
• Publish deb and rpms to repositories manually @Tyriar
• Add version with symbols to HockeyApp @Tyriar
• Enable scheduled insider builds @isidorn
• Twitter announcement @seanmcbreen

[isidorn]

We have done all the endgame duties. To make the release cleaner, I have created a seperate item for that thus closing this one in favor of #53579