morgand 02/04/10 10:02:41
Modified: xdocs releases.xml
Log:
fixed outdated hostnames and email addresses, also added more detail
abot Collections builds
Revision Changes Path
1.4 +26 -7 jakarta-commons/xdocs/releases.xml
Index: releases.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/xdocs/releases.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- releases.xml 28 Mar 2002 18:42:07 -0000 1.3
+++ releases.xml 10 Apr 2002 17:02:41 -0000 1.4
@@ -36,12 +36,12 @@
<ol>
<li>Announce your proposed release of a particular package to the
- <strong>[EMAIL PROTECTED]</strong> mailing list,
+ <strong>[EMAIL PROTECTED]</strong> mailing list,
and ask for a vote. Per the Commons Project charter, votes of
committers on the particular package in question (as listed in the
<code>STATUS.html</code> file) are binding.<br/><br/></li>
- <li>Log on to daedalus (via SSH) and create a new subdirectory for the
+ <li>Log on to jakarta.apache.org (via SSH) and create a new subdirectory for
the
release you are about to create. For example:
<pre>
cd /www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/
@@ -90,9 +90,9 @@
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
</pre></li>
- <li>Log in to daedalus and create the source distributions, based on the
+ <li>Log in to cvs.apache.org and create the source distributions, based on the
tag specified earlier, and move these files to the distribution
- directory as well. For example,
+ directory as well. For example (where "xyz" is your login),
<pre>
mkdir temp
cd temp
@@ -101,8 +101,8 @@
tar zcvf commons-foo-1.2-src.tar.gz commons-foo-1.2-src
zip -r commons-foo-1.2-src.zip commons-foo-1.2-src
rm -rf commons-foo-1.2-src
-mv commons-foo-1.2-src.* \
- /www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
+scp commons-foo-1.2-src.* \
+
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
</pre></li>
<li>Follow standard procedures to update the Jakarta web site (stored in
@@ -126,7 +126,7 @@
<ul>
<li>[EMAIL PROTECTED]</li>
<li>[EMAIL PROTECTED]</li>
- <li>[EMAIL PROTECTED]</li>
+ <li>[EMAIL PROTECTED]</li>
</ul><br/><br/></li>
</ol>
@@ -166,6 +166,25 @@
scp RELEASE-NOTES-1.2.html \
[EMAIL PROTECTED]:/www/jakarta.apache.org/builds/jakarta-commons/release/commons-foo/v1.2/
</pre></li>
+
+ <li>Update the <code>components.xml</code> and the
<code>collections.xml</code>
+ (including the link to the <code>STATUS.html</code>) files. Run the
+ <code>ant</code> command at the root of the <code>jakarta-commons</code>
+ module, which will build HTML versions of those documents in the
+ <code>docs</code> directory. Check in the generated docs.</li>
+
+ <li>Copy the API docs from the Collections build to the
+ <code>jakarta-commons/docs/collections/api</code> directory in CVS.
+ Be sure to <i>remove</i> Javadocs for any Collections that have been
+ permanently deleted.</li>
+
+ <li>Log onto jakarta.apache.org and perform a CVS update to grab the new
+ site documentation:
+
+<pre>
+cd /www/jakarta.apache.org/commons/
+cvs update
+</pre></li>
<li>Follow steps 10-11 above.</li>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
