Endgame Recovery Template
-
Create a milestone
<Month> <Year> Recoveryowner - Bump the version number owner
- 🔖candidate issues
- Assign candidate issues to the recovery milestone team
-
Review the
candidateissues, and if they pass the review assign them to the recovery milestone team -
All
candidatefixes are peer reviewed and pushed tomasterand then cherry-picked into the release branch team -
Initiate
insidersbuild frommaster -
Issues are tested in the
insidersteam -
Build
stablefor all platforms from release branch owner -
Issues are verified on
stablebuild and theverifiedlabel 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 (⚠️ MUST run with
--stable-buildargument ⚠️ )- Windows - owner
- OS X - owner
- Linux - owner
-
Sanity check of installable bits
-
Windows 32 bit owner
- signed installer 32-bit
- signed user installer 32-bit
- zip 32-bit
-
Windows 64 bit owner
- signed installer 64-bit
- signed user installer 64-bit
- zip 64-bit
-
Windows ARM64 owner
- signed installer ARM64
- signed user installer ARM64
- zip ARM64
- OS X - owner
-
Linux
- deb package 64-bit owner
- rpm package 64-bit owner
- archives owner
-
snap (
sudo snap install --classic --dangerous <file>.snap) owner
-
Server (instructions)
- Linux owner
- macOS owner
- Windows owner
-
Windows 32 bit owner
- Publish website @gregvanl
- 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: