Differences

This shows you the differences between two versions of the page.

--- development:git-branches [2020/06/11 18:15] – [Legacy Branches] demiankatz
+++ development:git-branches [2020/08/03 15:03] – demiankatz
@@ Line 1: / Line 1: @@
 ====== Useful Git Branches ======
-Some features are not available in the core VuFind distribution, either because they have been deprecated or because the VuFind team has not yet committed to maintaining them in the long term. These features are maintained in separate branches in the VuFind GitHub repository and may be merged in manually if they meet your local needs.
+Some features are not available in the core VuFind distribution, either because they have been deprecated, because they have not been released yet, or because the VuFind team has not yet committed to maintaining them in the long term. These features are maintained in separate branches in the VuFind GitHub repository and may be merged in manually if they meet your local needs.
+===== Core Branches =====
+Mainline VuFind development takes place in the "dev" branch. If you want "bleeding edge" code, this is the branch you should use.
+Whenever a major or minor release is issued, a maintenance branch is created so that bug fixes can be applied as needed. These maintenance branches are named "release-x.y" -- for example, "release-6.1" or "release-7.0". Note that patch releases do not get separate release branches, because we do not apply bug fixes against specific patch releases; we instead simply continue the "minor" release line. Every release receives a tag starting with "v" and the version number (e.g. "v6.1.2" or "v7.0").
+Summary:
+  * If you want the latest bleeding-edge code, use the "dev" branch.
+  * If you want the latest bug fixes for a particular major or minor release, use the matching "release-x.y" branch.
+  * If you want to get an exact release from a specific point in time, use the "vx.y.z" tag.
 ===== Feature Branches =====