svn commit: r1622971 - /db/jdo/HowToReleaseJDO.html

[cl...@apache.org]

Author: clr
Date: Sun Sep  7 05:09:37 2014
New Revision: 1622971

URL: http://svn.apache.org/r1622971
Log:
Update HowToReleaseJDO with new svnpubsub procedure

Modified:
    db/jdo/HowToReleaseJDO.html

Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=1622971&r1=1622970&r2=1622971&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Sun Sep  7 05:09:37 2014
@@ -126,7 +126,7 @@ https://svn.apache.org/repos/asf/db/jdo/
 	in the target directory of each subproject.
       </li>
       <li>Run RAT, which is at <a
-          href="http://incubator.apache.org/rat/">http://incubator.apache.org/rat/</a>,
+          href="http://creadur.apache.org/rat/">http://creadur.apache.org/rat/</a>,
         on the release. </li>
       </li>
       <li>
@@ -171,13 +171,21 @@ mvn release:perform -Papache-release
 		  https://docs.sonatype.org/display/Repository/Releasing+a+Staging+Repository">
 	   Releasing a Staging Repository</a> to release the artifacts.
 	</li>
+      <li>Update the distribution repository at http://apache.org/dist/db/jdo/
+        by adding the new release directory to the svnpubsub directory.
+        Check out the repository at 
+        https://dist.apache.org/repos/dist/release/db/jdo and add the
+        new release with all artifacts under the new directory. Make sure
+        that the key used to sign the artifacts is included in the KEYS file.
+        Committing the new directory will trigger an update to the mirrors.
+      </li>
       <li>If the release is a bug fix release to a maintenance release,
         update README.txt in the parent branch, adding the following
         line: "This release has been deprecated. Please use version
         2.x.y.", with a link to the svn web interface for that version.</li>
       <li>After updating the site (below), announce the release to the
         Apache community via email to announce@apache.org This must be
-        sent from an @apache.org email address. *** Be aware the by
+        sent from an @apache.org email address. *** Be aware that by
         sending to this address you will be bombarded with piles of
         emails from people with "I'm out of the Office" as if you really
         cared ***</li>
@@ -215,7 +223,11 @@ svn add site/docs/releases/release-<i>N.
         to the RunRules.html file of the latest release.</li>
       <li>Update the news list on the site home page to announce the new
         release.</li>
-      <li>Update the specification page to link to the new specification pdf document.
+      <li>Update the specification page to link to the new specification 
+        pdf document. If the release has been approved by the JCP, link
+        to the documentation page of the JCP web site. 
+        If the release has not been approved by the JCP, 
+        link to the .pdf in the JDO source repository.</li>
       <li>Add the javadoc for the release to the site.
         <ol>
           <li>Make a new directory under site/docs for the release, e.g.