Skip to content

August 2019 Endgame #79792

Closed
Closed
@alexdima

Description

@alexdima
  • Monday, 26 Aug Code freeze for the endgame
  • Friday, 30 Aug Endgame done
  • Wednesday, 4 Sep Expected release date (this may change)

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

DONE
Monday
  • Run OSS tool endgame master
    • 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 (using https://vscode-tools.azurewebsites.net/)
    • Run the tool multiple times to balance load if test items come in later and assignments are already made
  • 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
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
Friday
  • Pause scheduled insider builds endgame master
  • Satellite modules/npm packages ready, version updated, smoke tested
  • All issues verified
  • Fixing (only critical bugs - no string changes)
  • Smoketest (⚠️ MUST run with --stable-build argument ⚠️ )
  • Review pull requests acknowledgements with NOT MERGED - PLS REVIEW. endgame master
  • Acknowledge issue trackers from the community @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 endgame master
Friday/Monday
  • Branch code to `release/<x.y> endgame master
  • Bump up the version in package.json - endgame master
  • Announce master is open for business endgame master
  • Polish release notes redmond
Monday - Wednesday

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 endgame master
  • Make rpm signing request @Tyriar
  • Sanity check of installable bits
    • Windows 32 bit @alexr00
      • signed installer 32-bit
      • signed user installer 32-bit
      • zip 32-bit
    • Windows 64 bit @sandy081
      • signed installer 64-bit
      • signed user installer 64-bit
      • zip 64-bit
    • OS X - @jrieken
    • Linux
  • Publish website @gregvanl
  • Publish Localization language pack @weeteckt
  • Publish to stable endgame master
  • Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) endgame master
  • Publish @types/vscode endgame master
  • Publish rpm to repository manually @Tyriar
  • Enable scheduled insider builds endgame master
  • Twitter announcement @chrisdias

Metadata

Metadata

Assignees

Labels

endgame-planVS Code - Next release plan for endgame

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions