Closed
Description
- Create a milestone
<Month> <Year> Recovery
owner - Bump the version number owner
- 🔖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 tomain
and then cherry-picked into the release branch team - Initiate
insiders
build frommain
- Issues are tested in the
insiders
team - Build
stable
for all platforms from release branch owner - Issues are verified on
stable
build and theverified
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
- Sanity check of installable bits (server instructions)
- Windows 32 bit @alexdima
- signed installer 32-bit
- signed user installer 32-bit
- zip 32-bit
- server 32-bit
- Windows 64 bit @alexdima
- signed installer 64-bit
- signed user installer 64-bit
- zip 64-bit
- server 64-bit
- Windows ARM64 @bpasero
- signed installer ARM64
- signed user installer ARM64
- zip ARM64
- macOS
- Linux x64
- Linux server
- Windows 32 bit @alexdima
- Publish website @sana-ajani
- Publish stable build owner
- Create an official release owner
- Create a tag:
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
- Create a tag: