IGB Developer's Guide
Page tree

Versions Compared

Old Version 29

changes.mady.by.user Ann Loraine

Saved on

compared with

New Version 30

changes.mady.by.user Ann Loraine

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The IGB project uses git for version control. Previously, we used svn (subversion) and cvs. We migrated from an svn repository on SourceForge to a git repository on Bitbucket in 2014.

The repository address of the new IGB source code repository is: https://bitbucket.org/lorainelab/integrated-genome-browser.

When you clone from this repository, by default you'll get the 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 will come from this master branch.

Repository branches

IGB repository branches include:

  • Master branch - reflects the latest released code or the latest release candidate code (i.e. minor bug fixes which will be included in the next minor release versionsee preceding section).
  • Development branches - follow the conventional naming structure of igb_version (e.g. igb_8_2).  Only when creating a major release will the active development branches be merged with the stable (master) branch.  Once merged with the master branch, the development branch is discarded and a new development branch is created with the next major release version.

...