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.

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

April Endgame #25250

Closed
85 of 97 tasks
mjbvz opened this issue Apr 24, 2017 · 2 comments
Closed
85 of 97 tasks

April Endgame #25250

mjbvz opened this issue Apr 24, 2017 · 2 comments
Assignees
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone

Comments

@mjbvz
Copy link
Collaborator

mjbvz commented Apr 24, 2017

Endgame Schedule

  • April 25, Code freeze for the endgame
  • May 5, Endgame done

Tuesday, April 25

  • 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

Wednesday, April 26

  • Test plan items assigned
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Testing
  • Verification needed
  • Testing
  • Remind team members to assign issues that they intend to fix to the April milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification

Thursday, April 27

  • 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, April 28

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
@mjbvz mjbvz added the endgame-plan VS Code - Next release plan for endgame label Apr 24, 2017
@mjbvz mjbvz self-assigned this Apr 24, 2017
@jeremy447
Copy link

Do you think this one can be fixed for april release ?
#24309
Thanks !

@kieferrm kieferrm mentioned this issue Apr 25, 2017
15 tasks
@mjbvz mjbvz added this to the April 2017 milestone May 2, 2017
@mjbvz
Copy link
Collaborator Author

mjbvz commented May 5, 2017

Closing since 1.12 has shipped 🎆

@mjbvz mjbvz closed this as completed May 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.
Labels
endgame-plan VS Code - Next release plan for endgame
Projects
None yet
Development

No branches or pull requests

2 participants