Author: sebb
Date: Tue Apr 6 01:01:02 2010
New Revision: 930992
URL: http://svn.apache.org/viewvc?rev=930992&view=rev
Log:
JIRA: COMMONSSITE-50 Document KEYS update process for new RMs
Modified:
commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
URL:
http://svn.apache.org/viewvc/commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml?rev=930992&r1=930991&r2=930992&view=diff
==============================================================================
--- commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
(original)
+++ commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml Tue
Apr 6 01:01:02 2010
@@ -61,6 +61,28 @@
<a
href='http://www.apache.org/foundation/glossary.html#LazyConsensus'>lazy
consensus</a>.
</p>
<p>
+ If the release manager has not yet performed a Commons release, they may
need to add their
+ public key to the Commons KEYS file, which is located at:
+ <a href="https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS";>
+ https://svn.apache.org/repos/asf/commons/trunks-proper/KEYS</a>.
+ Note that the SVN directory contains externals for all "proper" Commons
components,
+ so use a command such as the following to check it out without
downloading every Commons project:
+ <pre>
+ svn co --depth=files
https://svn.apache.org/repos/asf/commons/trunks-proper/
+ </pre>
+ Once you have checked in the updated file,
+ update the copy in /www/www.apache.org/dist/commons/KEYS using
+ a command such as:
+ <code>scp KEYS people.apache.org:/www/www.apache.org/dist/commons</code>.
+ Alternatively, you can login to people.apache.org and update it there:
+ <pre>
+ cd /www/www.apache.org/dist/commons/
+ svn export http://svn.apache.org/repos/asf/commons/trunks-proper/KEYS
+ </pre>
+ The public key should also be
+ <a
href="http://www.apache.org/dev/release-signing.html#keyserver-upload";>uploaded
to a public keyserver</a>.
+ </p>
+ <p>
A release plan should also be prepared, in which the tasks remaining to
be done before
the release are listed. It may be useful to prepare draft release notes
before proposing
the release, so that others can see what changes are expected for the
new release.
