1**This is the documentation for etcd2 releases. Read [etcd3 doc][v3-docs] for etcd3 releases.** 2 3[v3-docs]: ../docs.md#documentation 4 5 6# Branch Management 7 8## Guide 9 10* New development occurs on the [master branch][master]. 11* Master branch should always have a green build! 12* Backwards-compatible bug fixes should target the master branch and subsequently be ported to stable branches. 13* Once the master branch is ready for release, it will be tagged and become the new stable branch. 14 15The etcd team has adopted a *rolling release model* and supports one stable version of etcd. 16 17### Master branch 18 19The `master` branch is our development branch. All new features land here first. 20 21If you want to try new features, pull `master` and play with it. Note that `master` may not be stable because new features may introduce bugs. 22 23Before the release of the next stable version, feature PRs will be frozen. We will focus on the testing, bug-fix and documentation for one to two weeks. 24 25### Stable branches 26 27All branches with prefix `release-` are considered _stable_ branches. 28 29After every minor release (http://semver.org/), we will have a new stable branch for that release. We will keep fixing the backwards-compatible bugs for the latest stable release, but not previous releases. The _patch_ release, incorporating any bug fixes, will be once every two weeks, given any patches. 30 31[master]: https://github.com/coreos/etcd/tree/master 32