You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by cr...@apache.org on 2004/07/19 16:16:06 UTC
svn commit: rev 23063 - forrest/trunk/etc
Author: crossley
Date: Mon Jul 19 07:16:05 2004
New Revision: 23063
Modified:
forrest/trunk/etc/RELEASE_PROCESS.txt
Log:
Start to tidy the release instructions.
Modified: forrest/trunk/etc/RELEASE_PROCESS.txt
==============================================================================
--- forrest/trunk/etc/RELEASE_PROCESS.txt (original)
+++ forrest/trunk/etc/RELEASE_PROCESS.txt Mon Jul 19 07:16:05 2004
@@ -8,6 +8,9 @@
Preparations
------------
+ - Ensure that as many PMC members as possible have their PGP keys in
+ the KEYS file.
+
- Edit module.xml and replace the '-dev' text with '':
...
<project name="xml-forrest">
@@ -45,6 +48,8 @@
- Test the distribution.
+ - FIXME: Describe how to sign releases and generate MD5 and PGP.
+
- If everything looks okay, tag CVS with 'cvs tag FORREST_xy', where 'xy' is a
compact form of the version (eg 04, 041, 05). Run 'cvs log build.xml' to
see existing tags.
@@ -59,32 +64,32 @@
Upload and announcement
-----------------------
- - Upload the binaries **and the RELEASE-NOTES** to daedalus. This is done by
- bugging Steven. Alternatively for people with daedalus access, I believe
- the process is documented at http://cvs.apache.org/~bodewig/mirror
-
- - Wait for the various mirrors to pick up the new file (see
- http://www.apache.org/dyn/closer.cgi/xml/forrest/). This has been known to
- take up to 10 hours.
-
- - Send an announcement email. Typically this is sent to
- announcements@xml.apache.org and announcements@jakarta.apache.org, with
- forrest-dev Cc'ed.
+ - Upload the binaries, the source archives, **and the RELEASE-NOTES**
+ to www.apache.org at /www/www.apache.org/dist/forrest/
+ Each PMC member has a server account and belongs to the forrest group.
+ The process is documented at http://cvs.apache.org/~bodewig/mirror.html
+
+ - Wait for the various mirrors to pick up the new files.
+ This has been known to take up to 10 hours. Test it via
+ http://forrest.apache.org/mirrors.cgi
+
+ - Send announcement email. Typically this is sent to
+ announcements@xml.apache.org and announcements@jakarta.apache.org,
+ with Cc to dev@forrest.apache,org
!! Always refer them to the mirror facility
- never mention the URL www.apache.org/ dist/ in email.
+ !! Never mention the URL www.apache.org/ dist/ in email.
As for the announcement format, see previous releases:
0.2: http://marc.theaimsgroup.com/?l=xml-apache-announce&m=103746673310573&w=2
0.3: http://marc.theaimsgroup.com/?l=xml-apache-announce&m=104399934113331&w=2
0.4: http://marc.theaimsgroup.com/?l=jakarta-announce&m=104510734501302&w=2
- - Ask Jeff to do the freshmeat (http://www.freshmeat.net/) announcement, or
- add you as an admin.
+ - Ask Jeff Turner to do the freshmeat (http://www.freshmeat.net/) announcement,
+ or add you as an admin.
- Edit xml-site/src/documentation/content/xdocs/news.xml and record the
- announcement, and then commit the new HTML to xml-site/targets/forrest (this
- can be done automatically from http://forrestbot.cocoondev.org).
-
+ announcement, and then commit the new HTML to xml-site/targets/forrest
+ Note that they still use forrest-0.5.1 to build their website.
Cleanups
--------
@@ -94,7 +99,7 @@
<project name="xml-forrest">
<version fix="0" major="0" minor="5" tag="-dev"/>
- - Edit src/resources/forrest-shbat/forrest.build.xml and update the version:
+ - Edit src/core/forrest.build.xml and update the version:
| Forrest Site Builder |
| 0.5 |