bayard 2004/05/29 14:29:42
Modified: commons-build/xdocs/releases prepare.xml
Log:
various bits I came across while building common-io 1.0
Revision Changes Path
1.10 +26 -5 jakarta-commons/commons-build/xdocs/releases/prepare.xml
Index: prepare.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/commons-build/xdocs/releases/prepare.xml,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -r1.9 -r1.10
--- prepare.xml 22 May 2004 00:11:50 -0000 1.9
+++ prepare.xml 29 May 2004 21:29:42 -0000 1.10
@@ -68,6 +68,7 @@
Implementation-Vendor: "Apache Software Foundation"
Implementation-Version: "1.3"
</pre>
+ <p>If building using Maven, this is done automatically. </p>
</subsection>
<subsection name='Bugzilla'>
<p>
@@ -81,7 +82,7 @@
</p>
</subsection>
<subsection name='Release Notes'>
- <p>
+ <p>
Different components have their own ways of creating release notes.
Here's the hard way!
</p>
@@ -91,8 +92,11 @@
Bugs fixed should be listed separately together with a short summary of the
bug.
A little time may be saved by checking the logs only for the source files.
</p>
- <p>
-Please remember to spell check the release notes. Please break lines at 80
characters.
+ <p>
+ Please remember to spell check the release notes. Please break lines at 80
characters.
+ </p>
+ <p>
+ Maven users may wish to use the changes.xml changelog report.
</p>
</subsection>
<subsection name='Test Against Listed Dependencies'>
@@ -103,6 +107,12 @@
dependency issues should probably be raised on the commons-dev list.
</p>
</subsection>
+ <subsection name='Ensure a good build.xml'>
+ <p>
+ If using Maven, ensure that 'maven ant' has been run so a usable build.xml
file exists,
+ and has the correct version.
+ </p>
+ </subsection>
<subsection name='Check the Apache License'>
<p>
Check the <a href="http://www.apache.org/licenses/";>Apache Licenses</a>
page for current information.
@@ -163,20 +173,31 @@
into the public folder <em>~/public_html</em> in your home directory
on <code>cvs.apache.org</code>.)
</p>
+ <p>
+ Remember to put up the website that will be deployed when the disributions
are released. You may
+ also want to show a unit-test code coverage report, using a tool such as
Clover or jCoverage,
+ and the differences since the previous version, using a tool like JDiff.
+ </p>
</subsection>
<subsection name='[VOTE] Release foo 1.0'>
+ <!-- Only cc PMC in on the RESULT. Votes require 3 +1s and no -1s. After a
period of time, 3 days to a week, send a RESULT email -->
<p>
Once the release candidate has been created and uploaded, now it's time to
propose the release VOTE.
</p>
<p>
- Post a <code>[VOTE] Release foo 1.0</code> email to <strong>[EMAIL
PROTECTED]</strong>
- and cc <strong>[EMAIL PROTECTED]</strong>. This should contain a link to
the release candidate.
+ Post a <code>[VOTE] Release foo 1.0</code> email to <strong>[EMAIL
PROTECTED]</strong>.
+ This should contain a link to the release candidate.
</p>
<p>
As per the Commons Project charter, votes of committers
on the particular package in question (as listed in the
<code>STATUS.html</code>) are binding.
If the <code>[VOTE]</code> is successful then continue. It is considered
good practice to allow
enough time for people to express their opinions.
+ </p>
+ <p>
+ Once a vote is successful, post a <code>[RESULT] Release foo 1.0</code>
email to
+ <strong>[EMAIL PROTECTED]</strong> as a reply to the original posting,
+ and cc <strong>[EMAIL PROTECTED]</strong>.
</p>
</subsection>
<subsection name='Final Preparations'>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
