Skip to content

November Endgame #64182

Description

@roblourens

Schedule Template

  • Dec 3 - Code freeze for the endgame
  • Dec 7 - Endgame done
  • Dec 12 - 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.

Monday
Tuesday
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 owner
Friday
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

Metadata

Metadata

Assignees

Labels

endgame-planVS Code - Next release plan for endgame

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions