Release Process

The release process is outlined as follows:

Requirements

• release happens when a milestone is reached, when all issues of a release are closed
• the devel branch enters code freeze and all the efforts are focused on using the tool and fixing bugs
• no open issues labeled as bugs should be present in devel branch for a reasonable amount of time (2 weeks?)

What happens at release time

• review the test coverage, double check that all the unit tests are passing
• review if there are new requirements for using the software (regarding the python version, as an example)
• sync with all the collaborators
• merge devel branch into master branch
• tag the master branch with the next release (release.sh or setup.py)
• update the main wiki page and readme.md
• create and upload the egg package (release.sh or setup.py)
• send out the news on the ML