Update item about release branches as we also create release branches for minor releases
parent
4326b961d2
commit
11bf58c2d1
|
@ -14,7 +14,7 @@ For core development, we use the following structure and flow.
|
|||
## Branches
|
||||
|
||||
* **Master** is the branch for all development and should always be the target of pull requests.
|
||||
* Each major release has a release branch e.g. `release/3.0`.
|
||||
* Each major or minor release has a release branch e.g. `release/3.0` or `release/3.2`. There are no release branches for patch releases.
|
||||
* Fixes are applied to master, and then **cherry picked into the release branch if needed**.
|
||||
* Features that are not for the next release (for major, when next is minor) get labelled 'major' and are left as PRs. They can be approved however.
|
||||
* Tags get created from release branches when ready to deploy.
|
||||
|
|
Loading…
Reference in New Issue