Return-Path:
example text
consistently assumes that preparation are being made to release
version 1.2 of component foo.
+Consider whether a release branch is needed. This is judgement call. A release branch increases the +complexity of the release but can help to prevent misunderstandings. Usually, for a small component +only good communication is needed. +
+
+These documents assume a release from CVS HEAD
. Some small modification to the procedure
+may be needed when using a release branch.
+
+
Different components have their own ways of creating release notes. Here's the hard way!
@@ -63,6 +74,10 @@ Go through the CVS logs for all source files which have changed since the last version. Analyse the log messages. Enhancements and new features need to be collated by topic. 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. + ++Please remember to spell check the release notes. Please break lines at 80 characters.
Now tag (for example
Once the vote has succeeded, then post a
Tag the release now. (This will ensure that there are no problems with badly timed commits.)
1.4 +1 -1 jakarta-commons/xdocs/releases/release.xml
Index: release.xml
===================================================================
RCS file: /home/cvs/jakarta-commons/xdocs/releases/release.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- release.xml 15 Apr 2003 11:48:38 -0000 1.3
+++ release.xml 25 Apr 2003 10:26:45 -0000 1.4
@@ -509,7 +509,7 @@
Please remember to give a brief description of you component. Please also remember to remind people
about verifying the signatures. The subject should be something like
This should go to (at least) the following mailing lists:
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
FOO_1_2_RC1
) and build distributions from that tag
- (as per full release). For commons components, it's usually unnecessary to post the
+ (as per full release). For commons components, it's usually unnecessary to post the
release candidate on the main release site. (It's usually good enough to upload it
into the public folder ~/public_html in your home directory
on cvs.apache.org
.)
@@ -122,7 +137,7 @@
[RESULT][VOTE] Release foo 1.0
email to
- commmons-dev@jakarta.apache.org and cc pmc@jakarta.apache.org.
+ commons-dev@jakarta.apache.org and cc pmc@jakarta.apache.org.
[ANNOUNCEMENT] Foo 1.2 Released
.
-You might like to send this mail from your apache account. Please spell check the document!
+Send this mail from your apache account. Please spell check the document!