...
When you clone from this repository, by default you'll getthe latest stable release candidate, also called the master branch. The master branch code is typically the same version of IGB that is available on the BioViz Web site. It may have some minor differences, typically bug fixes or low-risk new features. When we release a new version of IGB at BioViz, it comes from this master branch., the latest, most recent version of the code base.
Repository branches
IGB repository branches include:
- Master branch - reflects the latest released code or the latest release candidate code code under active development (see preceding section).
- Development Release branches - branches where we are developing new features in preparation for a new major release. Development corresponding to released version of IGB on BioViz.org. Release branches are named using the convention igb_[N]_[M] where N and M are integers (e.g. igb_8_2).
How
...
release branches correspond to IGB release names for users
When we distribute IGB to users, we assign version names such as 8.3.0 or 8.4.2, following the naming convention [N].[M].[P], where N, M, and P are integers. The N and M numbers come from the name of the development branch that was merged into the master branch before a major releaserelease branch name. The final ".P" suffix signifies low-risk, small changes that we merged from an upcoming development the master branch into the stable master a release branch and then distributed to users as a "minor" release.
A "major" release is anything that increments either first or second version number of IGB for users (e.g., 8.3.4 to 8.4.0 is a major release). When we do a major release, we merge the development branch into the master branch, stop making changes to the now obsolete development branch, and create a new development branch where we make further changescreate a release branch from the master branch.
A "minor" release is is anything that increments the final ".P" suffix version number of IGB for users (e.g., 8.3.0 to 8.3.1 is a minor release) and which requires merging a small amount of code from the development (master) branch into the master release branch.
Info |
---|
When developing IGB, you should make changes to the current development branch, not the master branch. For details, see Developing IGB. |
...