-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Release Process
João Moreno edited this page Jul 4, 2016
·
4 revisions
This page describes how we use branches and tags when we create an update:
- we use a branch such as
release/0.10.2
- then we build VSCode on that branch
- then do cross OS smoke testing
- then if we identify any critical issues we deliver fixes to the branch and repeat from step 2.
- when step 3 yields no additional critical (ship-blockers) issues we're done
- we then create a
0.10.2
tag and delete therelease/0.10.2
branch
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