4 Release Process

Rob Lourens редактировал(а) эту страницу 2022-11-01 15:42:33 -07:00

This page describes how we use branches and tags with every new release.

Example

1. During endgame, a release branch is created: release/1.10.
2. VS Code is functionally and smoke tested with a build from that branch.
3. Any critical issues should have fixes delivered to both main and release/1.10 and properly verified with step 2.
4. When there are no more additional critical issues, a release tag 1.10.0 is created.
5. VS Code is built from the 1.10.0 tag and shipped to customers.
6. 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
  • Issues Triaging
  • Community Issue Tracking
  • Automated Issue Triaging
  • Issue Grooming
• Build Champion
• Release Process
• Running the Endgame
  • Writing Test Plan Items
  • Sanity Check
• Related Projects

Contributing

• How to Contribute
• Submitting Bugs and Suggestions
  • Performance Issues
  • Keybinding Issues
  • Native Crash Issues
  • Search Issues
  • Terminal Issues
  • File Watcher Issues
  • TypeScript Issues
• Feedback Channels
• Source Code Organization
• Coding Guidelines
• Testing
  • Writing Tests
  • Smoke Test
• Dealing with Test Flakiness
• Contributor License Agreement
• Extension API Guidelines
• Accessibility Guidelines

Documentation

• Extensions
• API
• Visual Studio Code
• Document Repository
• Multi Root Workspace API

Want to contribute to this Wiki?

Fork it and send a pull request.