git workflow

We have switched to git / github  based development since the 3.3.0 release.

We use source code branches to handle our different release series.

• devel : the latest, most ambitious branch
• stable : the current release series
• integration : branches under consideration for next release

Most of the development happens in branches. Once ready for integration into stable or devel, a pull request is opened and a code review takes place. Here's a list of all branches in the works .

Contribute

Feel free to fork  our github repository  if you are willing to contribute!

History

We were using the monotone  source control system before our migration to git. All of the monotone database information was kept (commit content, messages, etc.) so if you need to go back in time you should be able to do so from the git repository. Still, our previous monotone code viewer interface  is still available if you need to browse the old repository.