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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

April 2022 - Recovery 2 #148935

Closed
46 of 49 tasks
joyceerhl opened this issue May 6, 2022 · 6 comments
Closed
46 of 49 tasks

April 2022 - Recovery 2 #148935

joyceerhl opened this issue May 6, 2022 · 6 comments
Assignees
Labels
endgame-plan

Comments

@joyceerhl
Copy link
Contributor

@joyceerhl joyceerhl commented May 6, 2022

  • Create a milestone <Month> <Year> Recovery endgame champion
  • Bump the version number endgame champion
  • 馃敄candidate issues
  • 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 candidate fixes are peer reviewed and pushed to main and then cherry-picked into the release branch team
  • Initiate insiders build from main
  • Issues are tested in the insiders team
  • Build stable for all platforms from release branch endgame champion
  • Issues are verified on stable build and the verified label is added endgame champion
  • Check https://github.com/Microsoft/vscode/compare/release/<x.y> to ensure no other commits have been made in the release branch endgame champion
  • Update the release notes and include a link to a query for the fixed issues @gregvanl
  • Sanity check of installable bits (server instructions)
  • Publish website @gregvanl
  • Publish stable build endgame champion
  • Create an official release endgame champion
    • Create a tag (make sure you pull the release branch first): git tag <x.y.z> release/<x.y>
    • Push the tag: git push origin <x.y.z>
    • Create a GitHub release: Open the GitHub tags, and click far right ... > Create Release. Use the correct title and description from our release notes. Example
  • Close the milestone on GitHub endgame champion
@joyceerhl joyceerhl added the endgame-plan label May 6, 2022
@joyceerhl joyceerhl pinned this issue May 6, 2022
@gjsjohnmurray
Copy link
Contributor

@gjsjohnmurray gjsjohnmurray commented May 7, 2022

Candidate issues link is using the wrong milestone.

@joyceerhl
Copy link
Contributor Author

@joyceerhl joyceerhl commented May 8, 2022

@gjsjohnmurray fixed, thanks!

@joyceerhl joyceerhl changed the title April 2022 - Recovery 1 April 2022 - Recovery 2 May 10, 2022
@joyceerhl joyceerhl self-assigned this May 13, 2022
@awwsssssssss

This comment was marked as spam.

@baby660122

This comment was marked as spam.

@joyceerhl joyceerhl added this to the April 2022 Recovery 2 milestone May 18, 2022
@joyceerhl joyceerhl unpinned this issue May 18, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Jul 2, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
endgame-plan
Projects
None yet
Development

No branches or pull requests

5 participants
@gjsjohnmurray @joyceerhl @awwsssssssss @baby660122 and others