Getting ConTroll™

ConTroll is available via GitHub in the repository https://github.com/MichaelRafferty/ConTroll.git.

Current Branch Structure

Master: The current ‘stable’ release branch. This trails the current release by one level until most sites are running the current release branch.

Test: Upcoming patches to the current stable release branch when master holds the current release. The current release when master still has the prior release as sites switch over.

Dev: A preview release of the next release (testing release) when master holds the current release. Upcoming patches to the current stable release branch when master still has the prior release as sites switch over.

<name>dev: A fast changing development branch. Commits to this branch may happen multiple times per day during active development periods. This is a good place to look for upcoming features, but not stable.

<convention> or <convention><number>: A branch that probably trails master used by a specific convention. It may, or may not, contain specific changes made by or for that convention.

Recommended Deployment Method

Whether or not you intend to make local changes to the code, it is recommended that you fork master and make your own repository. When you have code to contribute back you can make a pull request back to the original repository from that fork.

Please do not do any commits against branches directly in the ConTroll repository.