Skip to content

May 2019 Endgame #74412

Closed
Closed

Description

This is the endgame schedule for May 2019 Iteration.

Schedule

  • End game master: @rebornix / Redmond
  • End game buddy: @aeschli / Zurich
  • 05/28 Code freeze for the endgame
  • 05/31 Endgame done
  • 06/06 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.

Tuesday 05/28
  • Run OSS tool @aeschli
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Code freeze at 5pm CET
  • Ensure we have a green build on all platforms at 5pm CET
  • All test items contain test meta data by 5pm CET and sufficiently comprehensive test descriptions by 8am CET
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/
  • 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
  • Test build starts at 6pm CET
  • Test plan ready by 6pm CET
  • Testing
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Verification needed
  • Verification needed for Remote
Wednesday
  • Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification
  • Verification for Remote
Thursday
Friday/Monday
  • Branch code to `release/<x.y> @rebornix
  • Bump up the version in package.json - @rebornix
  • Announce master is open for business @rebornix
  • 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

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