Author: dennisl
Date: Wed Aug 1 04:05:14 2007
New Revision: 561760
URL: http://svn.apache.org/viewvc?view=rev&rev=561760
Log:
Update the KEYS sections, now that we use one central KEYS file.
Modified:
commons/proper/commons-build/trunk/xdocs/releases/release.xml
Modified: commons/proper/commons-build/trunk/xdocs/releases/release.xml
URL: http://svn.apache.org/viewvc/commons/proper/commons-build/trunk/xdocs/releases/release.xml?view=diff&rev=561760&r1=561759&r2=561760
==============================================================================
--- commons/proper/commons-build/trunk/xdocs/releases/release.xml (original)
+++ commons/proper/commons-build/trunk/xdocs/releases/release.xml Wed Aug 1 04:05:14 2007
@@ -138,7 +138,7 @@
<p>
OpenPGP (RFC2440) compatible detached signatures needed to be created for all releases.
Various applications can be used to create these signatures. For example,
- <a href='http://www.gnupg.org'>Gnu Privacy Guard</a> on linux:
+ <a href='http://www.gnupg.org'>Gnu Privacy Guard</a>.
</p>
<p>
See the <a href="http://www.apache.org/dev/release-signing.html#faq">Apache Release
Signing FAQ</a>
@@ -164,11 +164,11 @@
</pre>
</p>
<p>
- If this is the first release you personally have done for this component, then your code
+ If this is the first release you personally have done for Commons, then your code
signing public key must be added to the
- <a href='#Check KEYS file'><code>KEYS</code> file for the component</a>.
- which is in the distribution directory that the signed binaries will be uploaded into
- (/www/apache.org/dist/commons/{project} on people.apache.org).
+ <a href='#Check KEYS file'><code>KEYS</code> file for Commons</a>.
+ which is in the root of the Commons distribution directory
+ (/www/apache.org/dist/commons/KEYS on people.apache.org).
If this file is not present, it needs to be created.
</p>
</subsection>
@@ -301,7 +301,7 @@
<a name='Check KEYS file'/>
<strong>Check KEYS file</strong><br/>
Check the <code>KEYS</code> file located in the main release directory. This
should contain all the
- public keys which have been used to sign the component's releases. Make sure that this
file exists and
+ public keys which have been used to sign Commons' releases. Make sure that this file
exists and
that it contains the public key you've used to sign these releases. (The <code>KEYS</code>
file should
give instructions about how to do this.)
</p>
|