[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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 #29518

Closed
roblourens opened this issue Jun 27, 2017 · 2 comments
Closed

June endgame #29518

roblourens opened this issue Jun 27, 2017 · 2 comments
Assignees
@roblourens
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone
June 2017

Comments

@roblourens
Copy link
Member
roblourens commented Jun 27, 2017 •
edited by danyeh
Loading

Endgame Schedule

  • June 26, Code freeze for the endgame
  • July 7, Endgame done

Monday, June 26

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

Wednesday, June 28

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

Thursday, June 29

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

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
Tuesday, July 4 - Redmond holiday
  • Fireworks
  • Grill stuff
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
@roblourens roblourens added the endgame-plan VS Code - Next release plan for endgame label Jun 27, 2017
@roblourens roblourens added this to the June 2017 milestone Jun 27, 2017
@roblourens roblourens self-assigned this Jun 27, 2017
@kieferrm kieferrm mentioned this issue Jun 27, 2017
Closed
30 tasks
@roblourens
Copy link
Member Author
roblourens commented Jul 19, 2017 •
edited
Loading
  • Wed pm Redmond: build, validate issues are resolved, smoke test
  • Redmond: Publish insiders with new TS
  • Thu am Zurich: pick up latest bits, validate, smoke test
  • Thu am Redmond: Sync with Zurich, see if any new issue arise
  • Thu pm Redmond: ship 1.14.2

Release checklist

  • Create a milestone <Month> Recovery <year> @owner
  • Include an issue 'update translations' @owner
  • Assign candidate issues to the recovery milestone @team
  • Review the candidate issues, and if they pass the review assign them to the recovery milestone @team
  • All candiate fixes are peer reviewed and pushed to master and then cherry-picked into the release branch @team
  • Initiate insiders build from master
  • Issues are tested in the insiders @team
  • Build stable for all platforms from release branch @owner
  • Make rpm signing request @Tyriar
  • Issues are verified on stable build and the verified label is added @owner
  • Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch @owner
  • Update the release notes and include a link to a query for the fixed issues @gregvanl
  • Smoketest stable bits
  • Sanity check installable stable bits that have not been smoke tested
  • Publish website @gregvanl
  • Publish stable build @owner
  • Publish deb and rpms to repositories manually @Tyriar
  • Add a git tag to HEAD of release/<x.y> in format x.y.z

@joaomoreno
Copy link
Member

@roblourens Should this be closed?

@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.
Assignees

@roblourens roblourens

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

No branches or pull requests
2 participants
@joaomoreno @roblourens