IGB Developer's Guide
Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 22 Next »

Version Control

The Genoviz project uses Git for version control and managing the release cycle. Note that for many years, Genoviz used Subversion for version control. We migrated from Subversion to Git in 2014.

IGB code base

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

  • genometryImpl genomic data models shared by DAS server code and IGB
  • genoviz_sdk graphics framework that handles zooming, user interactions with data, etc.
  • 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

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.

Release Tags

When creating a release, a Git tag is created to annotate the point at which the release was built.

GenoPub project

For information about develop processes underway for the GenoPub project, please contact David Nix, Huntsman Cancer Institute

  • No labels