You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by do...@cocoon.apache.org on 2004/10/11 11:15:07 UTC
[Cocoon Wiki] Updated: CocoonReleaseHowTo
Date: 2004-10-11T02:15:07
Editor: BertrandDelacretaz <bd...@codeconsult.ch>
Wiki: Cocoon Wiki
Page: CocoonReleaseHowTo
URL: http://wiki.apache.org/cocoon/CocoonReleaseHowTo
Creating TestingBeforeRelease page
Change Log:
------------------------------------------------------------------------------
@@ -1,6 +1,7 @@
This info is for Cocoon committers who need to prepare a new release of Cocoon.
== See also ==
+ * TestingBeforeRelease
* CocoonWebsiteUpdate
* LatestRelease - please update that page when a release is done
----
@@ -22,19 +23,19 @@
* VARIANT identifies the "type of distribution" (ex. win32, jdk12, linux, jdk14...) (optional)
So, in Cocoon's case, all our archives shall be called something like:
-{{{
- cocoon-2.0.4-jdk14-bin.tar.gz
+{{{
+ cocoon-2.0.4-jdk14-bin.tar.gz
}}}
or
-{{{
- cocoon-2.1m1-src.zip
+{{{
+ cocoon-2.1m1-src.zip
}}}
and so on...
If one day we ever released some subproject code (for example Lenya), the
name should be along the lines of
-{{{
- cocoon-lenya-1.0-bin.tar.gz
+{{{
+ cocoon-lenya-1.0-bin.tar.gz
}}}
You get the point.
== B) The Release Process ==
@@ -58,9 +59,9 @@
=== Build the distrubtion ===
Make sure that you make a clean build and that you are really not using windows
-{{{
-# ./build.sh clean-dist
-# ./build.sh dist
+{{{
+# ./build.sh clean-dist
+# ./build.sh dist
}}}
=== Test the distribution ===
Unarchive the build distribution and test it. These tests should include
@@ -130,49 +131,49 @@
with the same structure. For example the final directory will look something
like:
-{{{www/www.apache.org/dist/cocoon/
-|
-+- BINARIES/
-| |
-| +- cocoon-2.0.3-bin.tar.gz
-| |
-| \- cocoon-2.0.4-bin.tar.gz
-|
-+- SOURCES/
-| |
-| +- cocoon-2.0.3-src.tar.gz
-| |
-| +- cocoon-2.0.4-src.tar.gz
-| |
-| +- cocoon-2.1m1-src.tar.gz
-| |
-| \- cocoon-2.1m2-src.tar.gz
-|
-+- OLD/
-| |
-| +- cocoon-1.8.1.tar.gz
-| |
-| \- cocoon-1.8.2.tar.gz
-|
-+- cocoon-latest-bin.tar.gz -> BINARIES/cocoon-2.0.4-bin.tar.gz
-|
-+- cocoon-latest-src.tar.gz -> SOURCES/cocoon-2.0.4-src.tar.gz
-|
-+- lenya/
-| |
-| +- BINARIES/
-| | |
-| | \- cocoon-lenya-1.0-bin.tar.gz
-| |
-| +- SOURCES/
-| | |
-| | \- cocoon-lenya-1.0-src.tar.gz
-| |
-| +- cocoon-lenya-latest-bin.tar.gz -> BINARIES/cocoon-lenya-1.0-bin.tar.gz
-| |
-| \- cocoon-lenya-latest-src.tar.gz -> SOURCES/cocoon-lenya-1.0-src.tar.gz
-|
-\- license.txt
+{{{www/www.apache.org/dist/cocoon/
+|
++- BINARIES/
+| |
+| +- cocoon-2.0.3-bin.tar.gz
+| |
+| \- cocoon-2.0.4-bin.tar.gz
+|
++- SOURCES/
+| |
+| +- cocoon-2.0.3-src.tar.gz
+| |
+| +- cocoon-2.0.4-src.tar.gz
+| |
+| +- cocoon-2.1m1-src.tar.gz
+| |
+| \- cocoon-2.1m2-src.tar.gz
+|
++- OLD/
+| |
+| +- cocoon-1.8.1.tar.gz
+| |
+| \- cocoon-1.8.2.tar.gz
+|
++- cocoon-latest-bin.tar.gz -> BINARIES/cocoon-2.0.4-bin.tar.gz
+|
++- cocoon-latest-src.tar.gz -> SOURCES/cocoon-2.0.4-src.tar.gz
+|
++- lenya/
+| |
+| +- BINARIES/
+| | |
+| | \- cocoon-lenya-1.0-bin.tar.gz
+| |
+| +- SOURCES/
+| | |
+| | \- cocoon-lenya-1.0-src.tar.gz
+| |
+| +- cocoon-lenya-latest-bin.tar.gz -> BINARIES/cocoon-lenya-1.0-bin.tar.gz
+| |
+| \- cocoon-lenya-latest-src.tar.gz -> SOURCES/cocoon-lenya-1.0-src.tar.gz
+|
+\- license.txt
}}}
== Publishing and linking: ==
@@ -186,35 +187,35 @@
for example, if the latest release is 2.0.4, and this release includes
3 different balls, 2 for binaries and 1 for sources, the following
links must be done:
-{{{
- # cd /www/www.apache.org/dist/cocoon
- # ln -s BINARIES/cocoon-2.0.4-vm14-bin.tar.gz cocoon-2.0.4-vm14-bin.tar.gz
- # ln -s BINARIES/cocoon-2.0.4-vm14-bin.zip cocoon-2.0.4-vm14-bin.zip
- # ln -s BINARIES/cocoon-2.0.4-bin.tar.gz cocoon-2.0.4-bin.tar.gz
- # ln -s BINARIES/cocoon-2.0.4-bin.zip cocoon-2.0.4-bin.zip
- # ln -s SOURCES/cocoon-2.0.4-src.tar.gz cocoon-2.0.4-src.tar.gz
- # ln -s SOURCES/cocoon-2.0.4-src.zip cocoon-2.0.4-src.zip
+{{{
+ # cd /www/www.apache.org/dist/cocoon
+ # ln -s BINARIES/cocoon-2.0.4-vm14-bin.tar.gz cocoon-2.0.4-vm14-bin.tar.gz
+ # ln -s BINARIES/cocoon-2.0.4-vm14-bin.zip cocoon-2.0.4-vm14-bin.zip
+ # ln -s BINARIES/cocoon-2.0.4-bin.tar.gz cocoon-2.0.4-bin.tar.gz
+ # ln -s BINARIES/cocoon-2.0.4-bin.zip cocoon-2.0.4-bin.zip
+ # ln -s SOURCES/cocoon-2.0.4-src.tar.gz cocoon-2.0.4-src.tar.gz
+ # ln -s SOURCES/cocoon-2.0.4-src.zip cocoon-2.0.4-src.zip
}}}
- A link to the latest milestone version for each tar/zipball (if present):
for example, if 2.1m1 publishes only one ball, the source one:
-{{{
- # cd /www/www.apache.org/dist/cocoon
- # ln -s SOURCES/cocoon-2.1-src.tar.gz cocoon-2.1-src.tar.gz
- # ln -s SOURCES/cocoon-2.1-src.zip cocoon-2.1-src.zip
+{{{
+ # cd /www/www.apache.org/dist/cocoon
+ # ln -s SOURCES/cocoon-2.1-src.tar.gz cocoon-2.1-src.tar.gz
+ # ln -s SOURCES/cocoon-2.1-src.zip cocoon-2.1-src.zip
}}}
- A link to the LATEST STABLE DOWNLOADABLE with the "version" string
replaced by the "latest" keyword. If the above example of 2.0.4 is still
valid:
-{{{
- # cd /www/www.apache.org/dist/cocoon
- # ln -s BINARIES/ccoon-2.0.4-vm14-bin.tar.gz cocoon-latest-vm14-bin.tar.gz
- # ln -s BINARIES/cocoon-2.0.4-vm14-bin.zip cocoon-latest-vm14-bin.zip
- # ln -s BINARIES/cocoon-2.0.4-bin.tar.gz cocoon-latest-bin.tar.gz
- # ln -s BINARIES/cocoon-2.0.4-bin.zip cocoon-latest-bin.zip
- # ln -s SOURCES/cocoon-2.0.4-src.tar.gz cocoon-latest-src.tar.gz
- # ln -s SOURCES/cocoon-2.0.4-src.zip cocoon-latest-src.zip
+{{{
+ # cd /www/www.apache.org/dist/cocoon
+ # ln -s BINARIES/ccoon-2.0.4-vm14-bin.tar.gz cocoon-latest-vm14-bin.tar.gz
+ # ln -s BINARIES/cocoon-2.0.4-vm14-bin.zip cocoon-latest-vm14-bin.zip
+ # ln -s BINARIES/cocoon-2.0.4-bin.tar.gz cocoon-latest-bin.tar.gz
+ # ln -s BINARIES/cocoon-2.0.4-bin.zip cocoon-latest-bin.zip
+ # ln -s SOURCES/cocoon-2.0.4-src.tar.gz cocoon-latest-src.tar.gz
+ # ln -s SOURCES/cocoon-2.0.4-src.zip cocoon-latest-src.zip
}}}
Make sure to change the "latest version" strings and URLs in the README.html
@@ -233,8 +234,8 @@
Remember that the locations to mention in any announcements when downloads
are involved is
-{{{
- http://cocoon.apache.org/mirror.cgi
+{{{
+ http://cocoon.apache.org/mirror.cgi
}}}
So that people will actually '''use''' the mirrors and not peg the Foundation's
bandwidth (which is quite expensive).