-
Notifications
You must be signed in to change notification settings - Fork 6
Release Process
Simone Marzona edited this page May 14, 2016
·
7 revisions
this is a draft
The release process is outlined as follows:
- 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?)
- review the test coverage, double check that all the unit tests are passing
- sync with all the collaborators
- merge devel branch into master branch
- tag the master branch with the next release
- update the main wiki page
- create and upload the egg package (release.sh)
- send out the news on the ML