Jump to: navigation, search

Difference between revisions of "SMILA/Release Work Checklist"

(Put builds on Eclipse download server)
Line 17: Line 17:
  
 
* In the following "$VERSION" is the release number.
 
* In the following "$VERSION" is the release number.
** milestones: e.g. "0.9-M1".
+
** milestones: e.g. "1.0-M1".
** releases: e.g. "0.9"
+
** releases: e.g. "1.0"
  
 
* <code>mkdir $VERSION</code>
 
* <code>mkdir $VERSION</code>

Revision as of 08:23, 24 January 2012

How to create a SMILA release or milestone

This page describes what to do to make a SMILA release or milestone available for download.

Check versions of SMILA bundles and packages

All bundles and packages should have version numbers equals to the release/milestone number (without the milestone part of sourse). I.e. for release 1.0 all versions should be set to 1.0.0.

Put builds on Eclipse download server

  • For milestones: cd /opt/public/rt/smila/milestones
  • For releases: cd /opt/public/rt/smila/releases
  • In the following "$VERSION" is the release number.
    • milestones: e.g. "1.0-M1".
    • releases: e.g. "1.0"
  • mkdir $VERSION
  • cp ../nightly/SMILA-*.zip $VERSION
  • rename the files by replacing the "r1234" part with $VERSION
  • For milestones: cp -R $VERSION /home/data/httpd/download.eclipse.org/rt/smila/milestones
  • For releases: cp -R $VERSION /home/data/httpd/download.eclipse.org/rt/smila/releases
  • Send URLs for download to a project lead to put them on the web pages (:

Make javadocs available

  • cd /opt/public/rt/smila/javadoc
  • cp -R current $VERSION
  • cd $VERSION
  • zip -r ../SMILA-javadoc-$VERSION.zip *