Author: sebb
Date: Mon May 2 15:53:12 2016
New Revision: 1741990
URL: http://svn.apache.org/viewvc?rev=1741990&view=rev
Log:
Update release prep notes
Modified:
commons/cms-site/trunk/content/xdoc/releases/prepare.xml
Modified: commons/cms-site/trunk/content/xdoc/releases/prepare.xml
URL:
http://svn.apache.org/viewvc/commons/cms-site/trunk/content/xdoc/releases/prepare.xml?rev=1741990&r1=1741989&r2=1741990&view=diff
==============================================================================
--- commons/cms-site/trunk/content/xdoc/releases/prepare.xml (original)
+++ commons/cms-site/trunk/content/xdoc/releases/prepare.xml Mon May 2
15:53:12 2016
@@ -661,8 +661,6 @@
structure for your component.</p>
<pre>
svn mkdir -m "Creating initial directory structure for foo"
https://dist.apache.org/repos/dist/dev/commons/foo
- svn mkdir -m "Creating initial directory structure for foo"
https://dist.apache.org/repos/dist/dev/commons/foo/binaries
- svn mkdir -m "Creating initial directory structure for foo"
https://dist.apache.org/repos/dist/dev/commons/foo/source
</pre>
<p>Then check out
<code>https://dist.apache.org/repos/dist/dev/commons/foo</code> and copy the
tarballs, checksums and
PGP signatures to the appropriate directories. You can find those
artifacts inside your local Maven repository.
@@ -671,15 +669,16 @@
version=1.2
repo_path=~/.m2/repository/org/apache/commons/commons-foo/${version}
release_path=~/foo-release
- mkdir -p ${release_path}/binaries
- mkdir -p ${release_path}/source
- cp ${repo_path}/*.bin.zip* ${release_path}/binaries
- cp ${repo_path}/*.bin.tar.gz* ${release_path}/binaries
- cp ${repo_path}/*.src.zip* ${release_path}/source
- cp ${repo_path}/*.src.tar.gz* ${release_path}/source
+ mkdir -p ${release_path}/FOO_1_2_RC1
+ cp ${repo_path}/*.bin.zip* ${release_path}/FOO_1_2_RC1
+ cp ${repo_path}/*.bin.tar.gz* ${release_path}/FOO_1_2_RC1
+ cp ${repo_path}/*.src.zip* ${release_path}/FOO_1_2_RC1
+ cp ${repo_path}/*.src.tar.gz* ${release_path}/FOO_1_2_RC1
cp RELEASE-NOTES.txt ${release_path}
</pre>
<p><code>svn add</code> the files and commit them. Again, record the
revision number for the vote email.</p>
+ There is a script which can be used to do all of this at:
+ <a
href="https://svn.apache.org/repos/asf/commons/scripts/Nexus2DistDev.sh";>https://svn.apache.org/repos/asf/commons/scripts/Nexus2DistDev.sh</a>
</subsection>
<subsection name='Create the Release Candidate Website'>
@@ -708,52 +707,71 @@
</p>
<p>
Post a <code>[VOTE] Release Foo 1.2 based on RC1</code> email to
<strong>d...@commons.apache.org</strong>.
- This should include links to minimally the distributions, site, tag
and KEYS. Here is an example release VOTE message body:
+ This should include links to minimally the distributions, site, tag
and KEYS.
+ Also the revisions for the various tags, and hashes for the release
artifacts
+ Here is an example release VOTE message body:
<pre>
- We have fixed quite a few bugs and added some significant enhancements since
Foo 1.1 was released,
- so I would like to release Foo 1.2.
+We have fixed quite a few bugs and added some significant enhancements since
Foo 1.1 was released,
+so I would like to release Foo 1.2.
- Foo 1.2 RC1 is available for review here:
- https://dist.apache.org/repos/dist/dev/commons/foo/ (svn revision XYZ)
+Foo 1.2 RC1 is available for review here:
+ https://dist.apache.org/repos/dist/dev/commons/foo/FOO_1_1_RC1 (svn
revision XYZ)
- Maven artifacts are here:
-
https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-foo/1.2/
+Maven artifacts are here:
+
https://repository.apache.org/content/repositories/orgapachecommons-NNNN/org/apache/commons/commons-foo/1.2/
- Details of changes since 1.1 are in the release notes:
- https://dist.apache.org/repos/dist/dev/commons/foo/RELEASE-NOTES.txt
+These are the Maven artifacts and their hashes
+
+commons-xyz-1.2-test-sources.jar
+(SHA1: abcd...)
+commons-xyz-1.2-sources.jar
+(SHA1: def...)
+... (no need for .asc hashes!)
+
+Details of changes since 1.1 are in the release notes:
+
https://dist.apache.org/repos/dist/dev/commons/foo/FOO_1_1_RC1/RELEASE-NOTES.txt
http://people.apache.org/~luckyrm/foo-1.2-RC1/changes-report.html
- I have tested this with JDK 1.3, 1.4, 1.5 and 1.6 using maven2.
+I have tested this with JDK 1.6, 7, 8 ... using Maven 3.x.x.
- The tag is here:
+ The tag is here:
http://svn.apache.org/repos/asf/commons/proper/foo/tags/FOO_1_2_RC1/ (svn
revision)
- N.B. the SVN revision is required because SVN tags are not immutable.
+ N.B. the SVN revision is required because SVN tags are not immutable.
- Site:
- http://people.apache.org/~luckyrm/foo-1.2-RC1/
+Site:
+ http://home.apache.org/~luckyrm/foo-1.2-RC1/
(note some *relative* links are broken and the 1.2 directories are
not yet created - these will be OK once the site is deployed)
- Clirr Report (compared to 1.1):
- http://people.apache.org/~luckyrm/foo-1.2-RC1/clirr-report.html
+Clirr Report (compared to 1.1):
+ http://home.apache.org/~luckyrm/foo-1.2-RC1/clirr-report.html
+
+Note that Clirr reports several errors.
+These are considered OK for the reasons stated below.
+These exceptions are also noted in the Changes and Release Notes.
+
+Errors reported:
+- methods added to interface: OK because that does not affect binary
compatibility.
+- etc.
- RAT Report:
- http://people.apache.org/~luckyrm/foo-1.2-RC1/rat-report.html
+RAT Report:
+ http://home.apache.org/~luckyrm/foo-1.2-RC1/rat-report.html
- KEYS:
+KEYS:
https://www.apache.org/dist/commons/KEYS
- Please review the release candidate and vote.
- This vote will close no sooner that 72 hours from now, i.e. after 0400 GMT
31-March 2010
+Please review the release candidate and vote.
+This vote will close no sooner that 72 hours from now,
+i.e. sometime after 04:00 UTC 31-March 2010
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
- Thanks!
+Thanks!
- Lucky RM </pre>
+Lucky RM </pre>
</p>
<p>
Votes from members of the Commons PMC are binding, however votes from
other committers, users and
