neos team mailing list archive
-
neos team
-
Mailing list archive
-
Message #00202
[Blueprint docu-stable-releases-checklist] (DOCU) Check list for stable releases
Blueprint changed by Johannes Wettinger:
Whiteboard changed:
+ 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"
+
+ 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) Commit changes of appResources.properties into the trunk repository
(2.3) Push the current revision to the mature branch of the relevant series
(2.4) Create executable JAR file by running the 'dist' target of revager-build.xml
(2.5) Create platform-specific versions of the application based on the newly created JAR file (Mac OS X, Windows)
(2.6) Set name of the files like "revager_<VERSION>.jar" or "revager_<VERSION>.exe"
(2.7) Create a ZIP file with the source of the released version and name it like "revager-src_<VERSION>.zip"
+ 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 team-neos.de for update notification
(3.3) Publish Release Notes / Changelog and News
(3.4) Update the screenshots on team-neos.de
--
(DOCU) Check list for stable releases
https://blueprints.launchpad.net/revager/+spec/docu-stable-releases-checklist