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

February Endgame #20981

Closed
60 of 63 tasks
joaomoreno opened this issue Feb 21, 2017 · 1 comment
Closed
60 of 63 tasks

February Endgame #20981

joaomoreno opened this issue Feb 21, 2017 · 1 comment
Assignees
@rebornix
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
February 2017

Comments

@joaomoreno
Copy link
Member

joaomoreno commented Feb 21, 2017 •
edited by egamma

Endgame Schedule

  • February, 2/21 Code freeze for the endgame
  • February, 2/28 Endgame done

Tuesday, February 21

  • 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, February 22

  • Test build starts at 7am CET / 10pm PT on Monday
  • Test plan ready by 8am CET / 11pm PT on Monday
  • Testing

Thursday, February 23

  • Testing
  • Remind team members to assign issues that they intend to fix to the July milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification Since there are quite some old bugs to verify we verify by age, youngest first. The queries are:

Friday, February 24

  • Fixing last issues
  • Verification
  • Add/update shrink-wrap files for built-in extensions if needed (see instructions) - endgame master
  • 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

Monday, February 27

Tuesday, February 28

  • Branch code to `release/<x.y> - endgame master
  • Announce master is open for business - endgame master
  • Polish release notes - @gregvanl

Wednesday, Mar 1

  • Merge translations - someone
  • Build stable for all platforms - @bpasero
  • Sanity check of installable bits
    • Windows - someone
    • OS X - someone
    • Linux - someone
  • Publish website @gregvanl
  • Publish to stable - someone
  • Publish deb and rpms to repositories manually - @Tyriar
  • Add a git tag to HEAD of release/<x.y> in format x.y.z
  • Enable scheduled insider builds - someone
  • Twitter announcement @seanmcbreen
@joaomoreno joaomoreno added the endgame-plan VS Code - Next release plan for endgame label Feb 21, 2017
@joaomoreno joaomoreno added this to the February 2017 milestone Feb 21, 2017
@kieferrm kieferrm mentioned this issue Feb 21, 2017
Closed
38 tasks
@egamma
Copy link
Member

egamma commented Mar 2, 2017

Closing 1.10 has shipped.

@egamma egamma closed this as completed Mar 2, 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

@rebornix rebornix

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

No branches or pull requests
3 participants
@joaomoreno @egamma @rebornix