The Relax-and-Recover project uses Github for source code management, issue tracking and this website.

Rear is fully developed with the bash language and we follow the coding styling described on the rear wiki page


The Relax-and-Recover project offers three mailinglists:

Reporting issues

The Github interface enables users to report issues or discuss improvements and new features through the issue-tracker at:

Once reported, one of the contributors can assign it to someone, classify it and attached it to a milestone release. Managing issues in this manner helps in collaborating, but also provides full transparency to users and contributors alike.

Release planning

New releases are planned based on outstanding issues, new features and ongoing development. You can get an overview of the various milestones the project has defined and you can influence new releases by reporting issues and by contributing fixes at:


If you are interested in contributing to Relax-and-Recover, you can discuss your area of interest on the users mailinglist, or you can simply fork the project on Github, make the modifications and then do a pull-request.

This makes it easy for the project to discuss the changes through the pull-request, and when accepted to merge the pull-request into the project.

Here is how to do it:

Fork the repository first and then clone your fork on your machine:

$ git clone
$ cd rear

Add a remote for the upstream repository:

$ git remote add upstream
$ git fetch upstream
* [new branch]      master     -> upstream/master

Create a new topic branch for the changes you want to make, based on the master branch from upstream:

$ git checkout -b fix-4-issue-999   upstream/master

Make your changes, test them, commit them and push them to Github:

$ git commit -a -m 'describe what you modified'
$ git push origin fix-4-issue-999

Open a Pull request from YOURNAME:fix-4-issue-999 to rear:master.

If you want to open another pull request for another change which is independant of the previous one, just create another topic branch based on the master branch from upstream ( git checkout -b fix-4-issue-999-2 upstream/master )

Finally, you can remove your branch fix-4-issue-999 when it has been merged in the rear:master branch.

$ git checkout master
$ git branch -D fix-4-issue-999

If you want to keep a fork, see also this article for an illustrated guide to keep your forked repo in sync.


We have a list of missing features that were requested but never got to a point of being implemented by the team members. If you feel an urgent need to see a missing feature added not hesitate to sponsor us in the ways listed

Professional services

If your company requires integrating Relax-and-Recover into their DRP setup or is interested to sponsor certain development, this is possible by the following companies that offer development services:

The various contributors have invested a lot in the creation and support of Relax-and-Recover.