Endgame Recovery Template
Alex Ross edited this page Feb 7, 2023
·
26 revisions
Pages 75
Project Management
- Roadmap
- Iteration Plans
- Development Process
- Issue Tracking
- Build Champion
- Release Process
- Running the Endgame
- Related Projects
Contributing
- How to Contribute
- Submitting Bugs and Suggestions
- Feedback Channels
- Source Code Organization
- Coding Guidelines
- Smoke Test
- Dealing with Test Flakiness
- Contributor License Agreement
- Extension API Guidelines
Documentation
Clone this wiki locally
- Create a milestone
<Month> <Year> Recovery <1|2|3>endgame champion - Bump the version number endgame champion
-
🔖 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 tomainand then cherry-picked into the release branch team - Initiate
insidersbuild frommain - Issues are tested in the
insidersteam - Build
stablefor all platforms from release branch endgame champion - Issues are verified on
stablebuild and theverifiedlabel 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)
- Windows 32 bit owner
- signed installer 32-bit
- signed user installer 32-bit
- zip 32-bit
- server 32-bit
- Windows 64 bit owner
- signed installer 64-bit
- signed user installer 64-bit
- zip 64-bit
- server 64-bit
- cli 64-bit
- Windows ARM64 owner
- signed installer ARM64
- signed user installer ARM64
- zip ARM64
- cli ARM64
- macOS
- Intel + Universal owner
- cli Intel
- Apple Silicon + Universal owner
- cli Silicon
- Linux x64 owner
- deb
- rpm
- archives
- snap (
sudo snap install --classic --dangerous <file>.snap) - cli
- Linux server owner
- x64
- x64 Alpine
- ARM32
- ARM64
- ARM64 Alpine
- Windows 32 bit owner
- 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
- Create a tag (make sure you pull the release branch first):
- Close the milestone on GitHub endgame champion