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

July Endgame #55349

Closed
sbatten opened this issue Jul 30, 2018 · 6 comments
Closed

July Endgame #55349

sbatten opened this issue Jul 30, 2018 · 6 comments
Assignees
@sbatten
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
July 2018

Comments

@sbatten
Copy link
Member

sbatten commented Jul 30, 2018 •
edited by gregvanl
Loading

  • July 30th: Code freeze for the endgame
  • August 3rd: Endgame done

Note: The Insiders build needs to be in the wild for 24 hours before we can enter the last phase of the endgame.

Note: Wednesday is a holiday for Zurich team and much of Zurich will be OOF throughout endgame.

Monday
  • 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
  • All closed feature-requests either have a verification-needed or on-testplan tag
  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Testing
  • Verification needed
  • Run OSS tool endgame master
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
Wednesday

Note: Holiday for Zurich

  • 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 Product: Visual Studio Code @sbatten @isidorn
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
  • Let Daniel Ye know that the release branch release/<x.y> got created and that translation should be pulled from there and that the pull request has to be created against that branch 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
  • Check translations (check i18n folder git history for latest translations, then build locally and see the amount of untranslated strings) @zurich
  • Build stable for all platforms endgame master
  • Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) endgame master
  • Make sure that the vsda module version in stable is the same as in insiders (which matches the latest electron)
  • Make rpm signing request @Tyriar
  • Sanity check of installable bits
  • Publish website @gregvanl
  • Publish to stable endgame master
  • Publish deb and rpms to repositories manually @Tyriar
  • Add version with symbols to HockeyApp @Tyriar
  • Enable scheduled insider builds endgame master
  • Twitter announcement @seanmcbreen
@sbatten sbatten added the endgame-plan VS Code - Next release plan for endgame label Jul 30, 2018
@sbatten sbatten added this to the July 2018 milestone Jul 30, 2018
@sbatten sbatten self-assigned this Jul 30, 2018
@egamma egamma mentioned this issue Jul 30, 2018
Closed
49 tasks
@endgame
Copy link

endgame commented Jul 30, 2018

Ha, github has subscribed me to your endgame plan. Awkward...

@ex1st
Copy link

ex1st commented Aug 4, 2018 •
edited by gregvanl
Loading

All release notes updated - release notes are collected in a file named v1_26.md

Seems link is wrong. - Fixed. Thanks for pointing this out.

@paterasMSFT
Copy link

Any updates here? Excited for 1.26!

@Tyriar
Copy link
Member

Tyriar commented Aug 10, 2018

@paterasMSFT we're aiming to go out early next week

@jens1o
Copy link
Contributor

jens1o commented Aug 11, 2018 •
edited
Loading

Why is this release delayed?

@Tyriar
Copy link
Member

Tyriar commented Aug 12, 2018

@jens1o to allow more time for stabilization.

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

@sbatten sbatten

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

No branches or pull requests
7 participants
@joaomoreno @endgame @Tyriar @sbatten @ex1st @jens1o @paterasMSFT