You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by st...@outerthought.org on 2003/04/29 19:00:05 UTC
[WIKI-UPDATE] Main TonyCollen OlderNews CocoonReleaseHowTo Tue Apr 29 19:00:05 2003
Page: http://wiki.cocoondev.org/Wiki.jsp?page=Main , version: 179 on Tue Apr 29 16:54:25 2003 by TonyCollen
- * March 19, 2003 ''-- [SW|SylvainWallez]''
- ** Added [RhinoWithContinuations] which explains continuations used in Cocoon's flow engine.
- ** Added [CleanerSiteMapsThroughResources] and [ResourceNaming] reflecting some recent insight [mpo|MarcPortier]
- * March 5, 2003
- ** Upped the JSPWiki engine to the current CVS version to fight the mysterious condition which causes JSPWiki to consume all available CPU for some unknown reason. Hope this helps. At the same time, cleaned up this page which has been altered for no particular reason. Go play in the [SandBox], please. ''-- [Steven Noels]''
- * February 25, 2003 ''-- [TC|TonyCollen]''
- ** Added [ResourceExistsAction]
- * February 24, 2003 ''-- [TC|TonyCollen]''
- ** Added [BlockDescriptions]
-
- * February 2003 ''-- [SN|Steven Noels]''
- ** Finished migration to the new skin and a new version of the JSPWiki engine. Lots of things happening on the Wiki, check out the [Cocoon Competence Center].
- ** Wiki change notification mails are now being sent to cocoon-docs@xml.apache.org - [Subscribe|mailto:cocoon-docs-subscribe@xml.apache.org] if you want uptodate Wiki news.
Page: http://wiki.cocoondev.org/Wiki.jsp?page=TonyCollen , version: 18 on Tue Apr 29 16:20:29 2003 by TonyCollen
+ My name is Tony, and I have been addicted to Cocoon for a little over a year now.
- This is my page.
- I like Cocoon.
- Apr 25 2003 - Working on [GettingStartedWithFlow]
+ My ICQ number is 12410567, feel free to contact me. I'm also available on {{coocon-users}} and {{cocoon-dev}} lists.
- Mar 21 2003 - Working on [DocsReorgProposal]
+ I am employed by the [University of Minnesota|http://www.umn.edu/]'s [Civil Engineering Department|http://www.ce.umn.edu/] as a web developer. My job is redesigning the current site which is there :)
+ !Worklog:
+ *Apr 25 2003 - Working on [GettingStartedWithFlow]
+ *Mar 21 2003 - Working on [DocsReorgProposal]
- Feb 25 2003 - Working on [ResourceExistsAction]
+ *Feb 25 2003 - Working on [ResourceExistsAction]
? +
+ *Feb 23 2003 - Working on [BlockDescriptions]
+ *Jan 8 2003 - Added and working on [Flow] (finally...)
+ *Nov 11 2002 - Added [PHPGenerator]
+ *Nov 1 2002 - Working on [SitemapPatterns]
+ *Older - [AboutTheBuildTargets]
+ !TODO:
+ *Intermediate Flow Docs
+ *Roll out weblog redesign
+ *openWeather
+ *SubShop
- Feb 23 2003 - Working on [BlockDescriptions]
-
- Jan 8 2003 - Added and working on [Flow] (finally...)
-
- Nov 11 2002 - Added [PHPGenerator]
-
- Nov 1 2002 - Working on [SitemapPatterns]
-
-
- Older - [AboutTheBuildTargets]
-
-
- My ICQ: 12410567
Page: http://wiki.cocoondev.org/Wiki.jsp?page=OlderNews , version: 6 on Tue Apr 29 16:54:52 2003 by TonyCollen
+ * March 19, 2003 ''-- [SW|SylvainWallez]''
+ ** Added [RhinoWithContinuations] which explains continuations used in Cocoon's flow engine.
+ ** Added [CleanerSiteMapsThroughResources] and [ResourceNaming] reflecting some recent insight [mpo|MarcPortier]
+ * March 5, 2003
+ ** Upped the JSPWiki engine to the current CVS version to fight the mysterious condition which causes JSPWiki to consume all available CPU for some unknown reason. Hope this helps. At the same time, cleaned up this page which has been altered for no particular reason. Go play in the [SandBox], please. ''-- [Steven Noels]''
+ * February 25, 2003 ''-- [TC|TonyCollen]''
+ ** Added [ResourceExistsAction]
+ * February 24, 2003 ''-- [TC|TonyCollen]''
+ ** Added [BlockDescriptions]
+ * February 2003 ''-- [SN|Steven Noels]''
+ ** Finished migration to the new skin and a new version of the JSPWiki engine. Lots of things happening on the Wiki, check out the [Cocoon Competence Center].
+ ** Wiki change notification mails are now being sent to cocoon-docs@xml.apache.org - [Subscribe|mailto:cocoon-docs-subscribe@xml.apache.org] if you want uptodate Wiki news.
Page: http://wiki.cocoondev.org/Wiki.jsp?page=CocoonReleaseHowTo , version: 1 on Tue Apr 29 16:45:24 2003 by BertrandDelacretaz
New page created:
+ This info is for Cocoon committers who need to prepare a new release of Cocoon.
+
+ It was (shamelessly) lifted from the cocoon-dev mailing list. Original message is (not available on marc.theaimsgroup.com yet).
+
+ !!!HOW TO DISTRIBUTE AN APACHE COCOON RELEASE
+ Notes on how to prepare a Cocoon release, by [Pier Fumagalli] on cocoon-dev.
+
+ !!A) Naming Conventions:
+
+ The name of each downloadable archive should be named after the following
+ regular expression:
+
+ {{{
+ PROJECT(-SUBPROJECT)?-VERSION(-VARIANT)?-(src|bin).(zip|tar.gz)
+ }}}
+
+ Where:
+ * PROJECT is the name of the top-level project,
+ * SUBPROJECT is the name of the eventual subproject (optional)
+ * VERSION is a version string (without - dashes)
+ * 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
+ }}}
+ or
+ {{{
+ 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
+ }}}
+ You get the point.
+
+ !! B) Directories:
+
+ The only (ONLY) place where distributions shall reside is inside the
+ /www/www.apache.org/dist/cocoon on daedalus.apache.org.
+
+ This directory contains three subdirectories:
+
+ * BINARIES: this is where the binary distribution tar/zipballs are located.
+ * SOURCES: this is where the source distribution tar/zipballs are located.
+ * OLD: all old and deprecated distributions.
+
+ In the future, when other subprojects of Cocoon will start putting out their
+ own releases, new directories will be created under the top level directory,
+ 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
+ }}}
+
+ !! Publishing and linking:
+
+ Once the distribution ball is rolled following the naming convention and
+ copied in the appropriate directory as outlined above, make sure that the
+ following links are present (and only those links) in the root directory for
+ the project/subproject:
+
+ - A link to the latest released stable version for each tar/zipball:
+ 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
+ }}}
+
+ - 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
+ }}}
+
+ - 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
+ }}}
+
+ Make sure to change the "latest version" strings and URLs in the README.html
+ and HEADER.html files in the /www/www.apache.org/dist/cocoon directory and
+ the mirror.html file in the /www/xml.apache.org/cocoon/ directory (once the
+ site gets moved to cocoon.apache.org it will be in the
+ /www/cocoon.apache.org/ directory)
+
+ Note that for release final downloads you shouldn't edit the mirrors.html
+ file, as the release should always be linked to cocoon-latest-.....
+
+ !! D) Mirroring and announcing:
+
+ Once the release is published wait at least 24 hours before announcing it to
+ the mailing lists, so that mirror sites will have the opportunity to pick
+ the changes up and you won't get bugged by people unable to download the
+ distributions.
+
+ Remember that the locations to mention in any announcements when downloads
+ are involved is
+ {{{
+ 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).
+
+ Have fun...
+
+ Pier
+ ----
+ !! Reader's notes
+ * When releasing, it would be a good idea to update the [LatestRelease] page here as well. -- [Bertrand Delacretaz]
+
+
+