neos team mailing list archive

[Johannes Wettinger <revager@xxxxxxxxxxxxxx>]

Blueprint changed by Johannes Wettinger:

Whiteboard changed:
- Step 1: Prepare the release
+ STEP 1: PREPARE THE RELEASE
  
- (1.1) Make sure the complete collection of unit tests run successfully!
- (1.2) Make sure the defined tests for the newly implemented features are successful!
- (1.3) Set the status of all feature requests in the Bug Tracker related to the implemented features to "Fix Released"
- (1.4) Set the implementation status of all blueprints related to the implemented features to "Informational"
+ 1.1. Make sure the complete collection of unit tests run successfully!
+ 1.2. Make sure the scenarios for the system test have been executed successfully!
+ 1.3. Set the status of all feature requests in the Bug Tracker related to the implemented features to "Fix Released"
+ 1.4. Set the implementation status of all blueprints related to the implemented features to "Implemented"
  
- Step 2: Create the release
+ STEP 2: CREATE THE RELEASE
  
- (2.1) Update version no., build no. and release date in appResources.properties (the build no. is the number of the current revision in the trunk repository plus 1)
- (2.2) Push the current revision to the mature branch of the relevant series
- (2.3) Create release files by running the 'release' target of revager-build.xml
- (2.4) Create DMG file by running the 'release' target of revager-build.xml on Mac OS X
+ 2.1. Make sure the translations (maintained by Launchpad Translations) are up-to-date
+ 2.2. Update version no., build no. and release date in appResources.properties (the build no. is the number of the current revision in the trunk repository plus 1)
+ 2.3. Push the current revision to the mature branch of the relevant series
+ 2.4. Create release files by running the 'release' target of revager-build.xml
+ 2.5. Create DMG file by running the 'release' target of revager-build.xml on Mac OS X
  
- Step 3: Publish the release
+ STEP 3: PUBLISH THE RELEASE
  
- (3.1) Release all created files of the new release on Launchpad.net
- (3.2) Update build no. and version no. on revager.org server for update notification
- (3.3) Publish Release Notes / Changelog and News
- (3.4) Update the screenshots on revager.org homepage
+ 3.1. Release all created files of the new release on Launchpad.net
+ 3.2. Update build no. and version no. on revager.org for update notification
+ 3.3. Publish release notes, changelog and news on Launchpad.net
+ 3.4. Update the screenshots on revager.org

-- 
(DOCU) Check list for stable releases
https://blueprints.launchpad.net/revager/+spec/docu-stable-releases-checklist