- 
                Notifications
    
You must be signed in to change notification settings  - Fork 35.9k
 
Release Process
        Rob Lourens edited this page Nov 1, 2022 
        ·
        4 revisions
      
    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 
mainandrelease/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. 
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
 - Custom ESLint rules
 
Documentation