forked from microsoft/vscode
-
Notifications
You must be signed in to change notification settings - Fork 0
Release Process
João Moreno edited this page Jul 4, 2016
·
2 revisions
This page describes how we use branches and tags with every new release.
Example
- During endgame, a release branch is created:
release/0.10.2. - VS Code is functionally and smoke tested with a build from that branch.
- Any critical issues should have fixed delivered to the branches
masterandrelease/0.10.2and properly verified with step 2. - When there are no more additional critical issues, a
0.10.2tag is created and therelease/0.10.2branch is deleted. - VS Code is built from the
0.10.2tag and shipped to customers.
Project Management
- Roadmap
- Iteration Plans
- Development Process
- Issue Tracking
- Release Process
- Running the Endgame
- Related Projects
Contributing
- How to Contribute
- Submitting Bugs and Suggestions
- Code Organization
- Coding Guidelines
- Smoke Test
- Contributor License Agreement
- Requested Extensions
Documentation