Skip to content

May Endgame #50477

Closed
Closed
@RMacfarlane

Description

@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

Wednesday

Thursday & Friday

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

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
  • 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

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