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

June Endgame #52781

Closed
isidorn opened this issue Jun 25, 2018 · 1 comment
Closed

June Endgame #52781

isidorn opened this issue Jun 25, 2018 · 1 comment
Assignees
@isidorn
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
June 2018

Comments

@isidorn
Copy link
Contributor

isidorn commented Jun 25, 2018 •
edited by gregvanl
Loading

  • June 25th: Code freeze for the endgame
  • June 29th: Endgame done
Monday
  • 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
  • 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 after merging shrink-wrap findings @isidorn
    • The LCA review of the ThirdPartyNotices.txt files is not needed anymore
Wednesday
  • Testing
  • Remind team members to assign issues that they intend to fix to the current milestone
  • Fixing (self-assigned, milestone assigned)
  • Verification
Thursday
Friday
Friday/Monday
  • Branch code to `release/<x.y> @isidorn
  • Bump up the version in package.json - isidorn
  • Announce master is open for business @isidorn
  • 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 @isidorn
  • 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
  • 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 @isidorn
  • Add a git tag to HEAD of release/<x.y> in format x.y.z (for vscode.d.ts download) @isidorn
  • new 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 @isidorn
  • Publish deb and rpms to repositories manually @Tyriar
  • Add version with symbols to HockeyApp @Tyriar
  • Enable scheduled insider builds @isidorn
  • Twitter announcement @seanmcbreen
@isidorn isidorn added the endgame-plan VS Code - Next release plan for endgame label Jun 25, 2018
@isidorn isidorn added this to the June 2018 milestone Jun 25, 2018
@isidorn isidorn self-assigned this Jun 25, 2018
@kieferrm kieferrm mentioned this issue Jun 25, 2018
Closed
52 tasks
@isidorn
Copy link
Contributor Author

isidorn commented Jul 5, 2018

We have done all the endgame duties. To make the release cleaner, I have created a seperate item for that thus closing this one in favor of #53579

@isidorn isidorn closed this as completed Jul 5, 2018
@thecodingdude thecodingdude mentioned this issue Jul 17, 2018
Closed
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 19, 2018
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
June 2018
Development

No branches or pull requests
1 participant
@isidorn