(DOCU) Checklist for Stable Releases
Checklist for new stable releases of RevAger
Blueprint information
- Status:
- Complete
- Approver:
- Team NEOS
- Priority:
- High
- Drafter:
- Johannes Wettinger
- Direction:
- Needs approval
- Assignee:
- Johannes Wettinger
- Definition:
- Approved
- Series goal:
- None
- Implementation:
-
Informational
- Milestone target:
- None
- Started by
- Johannes Wettinger
- Completed by
- Johannes Wettinger
Whiteboard
STEP 1: PREPARE THE RELEASE
* Make sure the complete collection of unit tests run successfully!
* Make sure the scenarios for the system test have been executed successfully!
* Set the implementation status of all blueprints related to the implemented features to "Implemented"
----
STEP 2: CREATE THE RELEASE
* Make sure the translations (maintained by Launchpad Translations) are up-to-date
* Update the version number in appResources.
* Create release files by running the 'bzr-release' target
* Commit content to trunk branch
* Push the current revision to the mature branch of the relevant series
* Create disk image file by running the 'release' target on Mac OS X
----
STEP 3: PUBLISH THE RELEASE
* Release all created files of the new release on Launchpad.net
* Update build no. and version no. on revager.org for update notification
* Publish release notes, changelog and news on Launchpad.net
* Update the screenshots on revager.org
----
STEP 4: UPDATE STATUS OF BUGS AND FEATURE REQUESTS
* Set the status of all feature requests and bugs in the Bug Tracker related to the implemented features and fixed bugs to "Fix Released"
