Version Control

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 address of the new IGB source code repository is https://bitbucket.org/lorainelab/integrated-genome-browser.

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 version).
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.

When developing IGB, you should make changes to the current development branch, not the master branch. For details, see Developing IGB.

IGB code base

The IGB repository is organized into sub-projects, including:

genometry - genomic data models used in IGB and the DAS server code
igb - the core IGB application
plugins - functions added via plug-in interface, plug-ins are also called bundles (uses OSGi)
common - common classes used by the other projects

Genoviz SDK

IGB depends on the Genoviz Software Development Kit (Genoviz SDK) which is version-controlled in a separate repository at https://bitbucket.org/lorainelab/genoviz-sdk. When you build IGB, the compilation tool we use (maven) will obtain the latest copy of the genoviz compiled code (a "jar" file) and install it locally.

Release Tags

When creating a release, we sometimes create a tag indicating at what point the release was built.

GenoPub project

For information about the GenoPub project, please contact David Nix, Huntsman Cancer Institute.