commons-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r930992 - /commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
Date Tue, 06 Apr 2010 01:01:02 GMT
Author: sebb
Date: Tue Apr  6 01:01:02 2010
New Revision: 930992

JIRA: COMMONSSITE-50 Document KEYS update process for new RMs


Modified: commons/proper/commons-site/trunk/src/site/xdoc/releases/prepare.xml
--- 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
@@ -61,6 +61,28 @@
       <a href=''>lazy consensus</a>.
+      If the release manager has not yet performed a Commons release, they may need to add
+      public key to the Commons KEYS file, which is located at:
+      <a href="">
+      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
+      <pre>
+        svn co --depth=files
+      </pre>
+      Once you have checked in the updated file,
+      update the copy in /www/ using
+      a command such as:
+      <code>scp KEYS</code>.
+      Alternatively, you can login to and update it there:
+      <pre>
+      cd /www/
+      svn export
+      </pre>
+      The public key should also be
+      <a href="">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.

View raw message