Changes between Version 9 and Version 10 of ReleaseProcedure

Timestamp:

Sep 22, 2014, 10:00:53 AM (10 years ago)

Author:

djay

Comment:

--

ReleaseProcedure

@@ -5 +5 @@
  * That file should include new features, changed features, and deprecated features if any. Changes to the official documentation should be specifically noted along with other items that will cause breaking changes during upgrades. 
  * Read the documentation and remove outdated parts.
- * Create release candidate as .zip and .tar.gz  then add them on this [http://zoo-project.org/site/Downloads page] (by editing this wiki page: [http://zoo-project.org/trac/wiki/Downloads ref.])
+ * Create release candidate as .zip and .tar.bz2  then add them on this [http://zoo-project.org/site/Downloads page] (by editing this wiki page: [http://zoo-project.org/trac/wiki/Downloads ref.])
  * Cut a release candidate once you think that everything is in order. Announce the release candidate for review for at least 1 week. In this period of time, it is also appropriate for you to deploy in production since you are asserting that it is stable and (significant) bug free. Publish a specific revision with this.
  * If significant bugs are reported, fix and cut a new release candidate. If no major bugs, then announce that the release candidate has officially been promoted to the official release (if you want, you can do this with a motion and support of the PSC).
@@ -39 +39 @@
 }}}
 
+ * Create version archives
+
+{{{
+   export VERSION=2.6.0
+   cd zoo-propject-svn
+   cp -r trunk zoo-project-$VERSION
+   cd zoo-project-$VERSION
+   rm -rf $(find ./ -name ".svn") 
+   cd zoo-project/zoo-kernel
+   autoconf
+   cd ../../..
+   tar -cvjf ./zoo-project.$VERSION.tar.bz2 ./zoo-project-$VERSION
+   zip -r ./zoo-project-$VERSION.zip ./zoo-project-$VERSION
+}}}