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

March Endgame #46620

Closed
sandy081 opened this issue Mar 27, 2018 · 6 comments
Closed

March Endgame #46620

sandy081 opened this issue Mar 27, 2018 · 6 comments
Assignees
Labels
endgame-plan VS Code - Next release plan for endgame
Milestone

Comments

@sandy081
Copy link
Member

sandy081 commented Mar 27, 2018

Endgame Schedule

  • March 26th, Code freeze for the endgame
  • March 30th, 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.

Monday

  • Code freeze at 5pm PT
  • Ensure we have a green build on all platforms at 5pm PT
  • All test items are created (with "complexity" but not necessarily with full description) by 5pm PT
  • All test items contain comprehensive test descriptions by 10pm PT
  • Update your availability for testing here - https://vscode-tools.azurewebsites.net/

Tuesday

Wednesday

Thursday & Friday

Monday week 2

  • If not done on Friday
    • 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 @gregvanl

Monday week 2 - Wednesday week 2

Thursday/Friday week 2

  • Merge translations PR (if it makes it in time) endgame master
  • 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 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
@sandy081 sandy081 added the endgame-plan VS Code - Next release plan for endgame label Mar 27, 2018
@sandy081 sandy081 added this to the March 2018 milestone Mar 27, 2018
@borekb
Copy link

borekb commented Apr 4, 2018

Out of curiosity, what does "Endgame done" date mean? I think that during the past few iterations, it has always been at the end of week 1 while the endgame always seems to be planned to last two weeks.

Awesome release documentation BTW :)

@Tyriar
Copy link
Member

Tyriar commented Apr 4, 2018

@borekb at the top it's referring to the team's test/verification week. The following week we refer to as debt week and we focus on technical debt reduction and fix any remaining issues with the build that pop up. More info here https://github.com/Microsoft/vscode/wiki/Development-Process#inside-an-iteration 😄

@borekb
Copy link

borekb commented Apr 4, 2018

Hmm, that wiki also seems to assume a single-week endgame which I don't think I've ever seen :)

But overall, I could measure month's progress just by looking at the GitHub Milestone progress bar, it's extremely impressive how predictably you deliver VSCode in a relatively large and distributed team. 🙇

@egamma
Copy link
Member

egamma commented Apr 9, 2018

Hmm, that wiki also seems to assume a single-week endgame which I don't think I've ever seen :)

@borekb the endgame is one week and the 'Endgame Done' date refers when the engineering work for the release is done. This date is different from when we ship the release. As @Tyriar explains above, after 'Endgame done' we let the release sit. We freeze the insiders channel so that we all test the latest bits and watch for critical issues. We review the critical issues daily. If there is a critical fix we wait for another 24 hours. Therefore the release date is during the week after the endgame, but we never release on a Friday. I´ll update the wiki with more detail. Given this I cannot remember an endgame that lasted longer than a week 💪, but glad to see your interest into our planning!

@egamma
Copy link
Member

egamma commented Apr 9, 2018

Closing 1.22 has shipped.

@egamma egamma closed this as completed Apr 9, 2018
@borekb
Copy link

borekb commented Apr 9, 2018

@egamma thanks for the explanation, makes perfect sense.

@vscodebot vscodebot bot locked and limited conversation to collaborators May 24, 2018
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

5 participants