Repository Management

This page outlines aspects of repository management including our branching strategy.

Bringing Changes to Trunk

Following a standard pattern of development moderated by GitHub, we maintain a trunk branch (called "master") in the metomi/fab repository. Each developer forks their own copy of this repository which is where they make their changes. Development branches are made on these personal forks and "Pull Requests" are raised back to the original repository trunk branch.

Version numbering

We follow the standard major, minor, patch version numbering scheme.

Changes in major version number imply an API breakage. Changes in minor version number implies new functionality. Changes in patch number implies bug fixes.

Release Branches

Releases are made from a release branch. This allows continued development on trunk.

Major and minor releases cause a fresh release branch to be made, picking up the new features added to trunk since the previous major or minor release. Bug fixes are applied to trunk and back ported to the current release branch. Patch releases are then made from that release branch.