Version Numbers

With the transition from the older subversion repository to github, we are introducing a new, simplified versioning scheme. The last formal version number of QuickReduce in subvservion was 2.0.5. The first formal release in github will be version 2.1.

• From now on, releases are integer increments in the minor version number. I.e., the next formal release will be version 2.2, 2.3, ...2.1000, etc.

• Minor adjustments within a release number (of technical nature that do not affect the results of the pipeline will be tracked via the git commit hash.

• Major revision number increases will be used as seen appropriate.

Git management

Source code is managed in two major branches:

• master, which will contain a tested version of the pipeline. The head of the master can be considered a release candidate that represents the cutting edge development until resources are available to make a formal release of QuickReduce into PPA (i.e., after finishing documentation, preparing user notification etc.)
• formal releases: A formal versioned release will originate in a new branch named release_X.XX (version number), branching of master. Technical adjustments to the code will be propagated in that branch. Examples of such changes include references to catalog host names etc.
• development, which is the baseline for any new feature development. New feature developments will branch of this development branch and will be merged back into development. After testing, the head of the development branch will be merged back into the master branch,

Deployment into PPA

PPA by default shall run the head of the agreed-upon and announced release branch.