-
Notifications
You must be signed in to change notification settings - Fork 30k
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 2022 - Recovery 1 #146388
Labels
endgame-plan
VS Code - Next release plan for endgame
Comments
1.66.1 is released! 🎉 |
FYI the link on the VS Code updates page is broken: |
@an-boxbrite fixed. I named the milestone Recovery |
👍 Unfortunately now the link on the release page is broken, still points at "...Recovery 1" |
I think we're all good here now. Can you confirm it's fixed on your end? |
Fixed the release page as well. |
Thanks! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
<Month> <Year> Recovery
endgame championcandidate
issues, and if they pass the review assign them to the recovery milestone teamcandidate
fixes are peer reviewed and pushed tomain
and then cherry-picked into the release branch teaminsiders
build frommain
insiders
teamstable
for all platforms from release branch endgame championstable
build and theverified
label is added endgame championhttps://github.com/Microsoft/vscode/compare/release/<x.y>
to ensure no other commits have been made in the release branch endgame championsudo snap install --classic --dangerous <file>.snap
)git tag <x.y.z> release/<x.y>
git push origin <x.y.z>
... > Create Release
. Use the correct title and description from our release notes. ExampleThe text was updated successfully, but these errors were encountered: