Release Process
João Moreno edited this page Mar 10, 2017
·
3 revisions
Pages 70
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
This page describes how we use branches and tags with every new release.
Example
- During endgame, a release branch is created:
release/1.10. - VS Code is functionally and smoke tested with a build from that branch.
- Any critical issues should have fixed delivered to both
masterandrelease/1.10and properly verified with step 2. - When there are no more additional critical issues, a release tag
1.10.0is created. - VS Code is built from the
1.10.0tag and shipped to customers. - Any further recovery builds should be from commits on the
release/1.10branch and patch versions should be used:1.10.1,1.10.2, etc.