Release Management

Unlike continuous integration, releases must be performed locally.
Performing a release means running specific Maven commands on a Git repository.
We do not release a single Maven module, but a set of coherent projects. A Git repository defines the bounds of this coherence.


  1. You must have an account at
  2. You must have been added as a manager on Roboconf @ Sonatype. See this ticket.
  3. You must have a signing key, generated with PGP. See these instructions.

Release Scripts

A project with release scripts is available on Github.
Clone it on your local repository. Scripts are numbered to indicate in which order they should be executed.

These scripts will check out the project from Github in the temporary directory.
It is assumed the release is performed under Linux (Debian systems essentially), with a JDK 7 or JDK 8.

1. indicates the process to follow.
2. Copy to
Add your Bintray credentials in it. This file is already listed in the .gitignore file.

3. Copy to
Add your credentials for Docekr Hub in this file. It is already listed in the .gitignore file.

4. Update the file with the new release information.
5. Release the web administration first (
6. Release the platform then.

Use for major and minor releases (e.g. 0.6, 0.7, etc).
Use for maintenance releases (e.g. 0.6.1, 0.6.2, etc).

Then go to Login and check the staging repositories. You should find one about Roboconf. Verify the content and then click close. Sonatype will then verify some quality rules about your upload (sources JAR, javadoc JAR…). Once this is done, click release.

7. Wait for the platform to be available on Maven Central.
This can take some minutes (generally about 20 minutes). Next scripts can be executed in any order. The order we defined is somehow arbitrary.


The platform is the only project that stores releases on Maven.
Some projects store their snapshots on Maven but not for releases (e.g. system installers).

For details about the manual release process, please refer to this page.