Assuming there is a unified version of the software and it's been already tested with success, the process of making a release may take place.
Release and documentation
- Create a branch in the code repository, with the software to be released.
- Double check software version number is correctly written in assembly/pom.xml and build assembly.
- Upload assembly (both .zip and tar.gz) in dev.mantychore.eu.
- Update user documentation with information about what has changed. Put additional emphasis in new features and changes in the user interface.
- Create a page in this wiki for the release under http://jira.i2cat.net:8090/display/MANTECH/Releases
Introduce the release changes. If the release is being tracked in JIRA (as end-of-sprint releases are), you may take the release changes from the Release Notes page (e.g: http://jira.i2cat.net:8080/secure/ReleaseNote.jspa?projectId=10720&version=11041).

Notice that unfinshed tasks (if any) are also included here, so they should be manually removed, and should not appear in the release page. - Put a reference to files uploaded in step 3.
- Refer to user documentation pages introducing changes, the ones in step 4.
- Add a section for identified bugs and link there bugs affecting this release.
Dissemination
- Send an email to mailing lists
- opennaas dev and users
- mantychore technical and internal
- Make a small post with the release announcement in Mantychore Official Web page (www.mantychore.eu)
Labels: