Branch Strategy
David Ko edited this page Aug 10, 2023
·
2 revisions
For each feature release branch, there will be a dedicated branch for the following repos. The branch name will be v..x.
- https://github.com/longhorn/longhorn-manager
- https://github.com/longhorn/longhorn-instance-manager
- https://github.com/longhorn/longhorn-engine
- https://github.com/longhorn/longhorn-spdk-engine
- https://github.com/longhorn/longhorn-share-manager
- https://github.com/longhorn/backing-image-manager
For each feature release branch, there will be a dedicated branch for the following repos. The branch name will be v..x.
There are no branch strategies for the library repos, because the design should be always backward compatible.
However, there have been two exceptions to this rule in the past. We made some incompatible changes to the main branch that were unable to be used in 1.3 and 1.4. We had to create two new branches, v1.3.x and v1.4.x, to support these older versions.