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

May Endgame #27415

Closed
aeschli opened this issue May 29, 2017 · 3 comments
Closed

May Endgame #27415

aeschli opened this issue May 29, 2017 · 3 comments
Assignees
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone

Comments

@aeschli
Copy link
Contributor

aeschli commented May 29, 2017

Endgame Schedule

  • May 29, Code freeze for the endgame
  • June 9, Endgame done

Monday, May 29

  • 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, May 30

Wednesday, May 31

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

Thursday, June 1

  • 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, June 2

Friday/Monday
  • Disable continuous 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 version with symbols to HockeyApp @bpasero
  • 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
@aeschli aeschli added the endgame-plan VS Code - Next release plan for endgame label May 29, 2017
@aeschli aeschli added this to the May 2017 milestone May 29, 2017
@aeschli aeschli self-assigned this May 29, 2017
@kieferrm kieferrm mentioned this issue May 29, 2017
44 tasks
@LiPengfei19820619
Copy link

HI, when will the download of win64 version be available?
Thanks a lot.

@egamma
Copy link
Member

egamma commented Jun 9, 2017

@LiPengfei19820619 we have a zip install only (see the May plan). The May plan has several limitations like no auto update. We have therefore decided to not make it available yet. More work is needed in June.

@egamma
Copy link
Member

egamma commented Jun 9, 2017

Closing - 1.13. has been shipped

@egamma egamma closed this as completed Jun 9, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 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

3 participants