Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

November Endgame #64182

Closed
roblourens opened this issue Dec 3, 2018 · 1 comment
Closed

November Endgame #64182

roblourens opened this issue Dec 3, 2018 · 1 comment
Assignees
@roblourens
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
November 2018

Comments

@roblourens
Copy link
Member

roblourens commented Dec 3, 2018 •
edited by shawndon
Loading

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
  • 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 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
@roblourens roblourens added the endgame-plan VS Code - Next release plan for endgame label Dec 3, 2018
@roblourens roblourens added this to the November 2018 milestone Dec 3, 2018
@roblourens roblourens self-assigned this Dec 3, 2018
@myfairsyer myfairsyer mentioned this issue Dec 3, 2018
Closed
45 tasks
@shawndon
Copy link

Singing off for Loc

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 26, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@roblourens roblourens

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
November 2018
Development

No branches or pull requests
2 participants
@roblourens @shawndon