forked from microsoft/vscode
-
Notifications
You must be signed in to change notification settings - Fork 7
Release Process
Alexander Frick edited this page May 17, 2024
·
1 revision
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 fixes delivered to both
main
andrelease/1.10
and properly verified with step 2. - When there are no more additional critical issues, a release tag
1.10.0
is created. - VS Code is built from the
1.10.0
tag and shipped to customers. - Any further recovery builds should be from commits on the
release/1.10
branch and patch versions should be used:1.10.1
,1.10.2
, etc.
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
- Testing
- Dealing with Test Flakiness
- Contributor License Agreement
- Extension API Guidelines
- Accessibility Guidelines
Documentation