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

March Endgame #23276

Closed
90 of 98 tasks
isidorn opened this issue Mar 27, 2017 · 1 comment
Closed
90 of 98 tasks

March Endgame #23276

isidorn opened this issue Mar 27, 2017 · 1 comment
Assignees
@isidorn
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
March 2017

Comments

@isidorn
Copy link
Contributor

isidorn commented Mar 27, 2017 •
edited by roblourens
Loading

Endgame Schedule

  • March 27 Code freeze for the endgame
  • April 4 Endgame done

Monday, March 27

  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms
  • All test items contain sufficiently comprehensive test descriptions by 6pm PT

Tuesday, March 28

  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Test plan items assigned
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Testing
  • Verification needed

Wednesday, March 29

  • Testing
  • Remind team members to assign issues that they intend to fix to the March milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification

Thursday, March 30

  • Fixing last issues
  • Verification
  • Run OSS tool after merging shrink-wrap findings endgame master
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
  • Check new OSS usage is entered into the OSS registry endgame master
Friday
Friday/Monday
  • Freeze insider builds - endgame master
  • Branch code to release/<x.y> and release master - 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.

Thursday/Friday
  • Merge translations @zurich
  • Build stable for all platforms endgame master
  • Make rpm signing request @Tyriar
  • Sanity check of installable bits
  • Publish website @gregvanl
  • Publish to stable @owner
  • Publish deb and rpms to repositories manually @Tyriar
  • 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
@isidorn isidorn added the endgame-plan VS Code - Next release plan for endgame label Mar 27, 2017
@isidorn isidorn added this to the March 2017 milestone Mar 27, 2017
@isidorn isidorn self-assigned this Mar 27, 2017
@kieferrm kieferrm mentioned this issue Mar 27, 2017
Closed
58 tasks
@stef-levesque stef-levesque mentioned this issue Apr 4, 2017
Closed
@rebornix
Copy link
Member

rebornix commented Apr 5, 2017

Closing as 1.11 has shipped.

@rebornix rebornix closed this as completed Apr 5, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@isidorn isidorn

Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Milestone
March 2017
Development

No branches or pull requests
2 participants
@rebornix @isidorn