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

[an...@apache.org]

Author: andyj
Date: Wed May 20 09:23:26 2009
New Revision: 776635

URL: http://svn.apache.org/viewvc?rev=776635&view=rev
Log:
update to announce@apache.org email

Modified:
    db/jdo/HowToReleaseJDO.html

Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=776635&r1=776634&r2=776635&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Wed May 20 09:23:26 2009
@@ -232,7 +232,8 @@
     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@general.apache.org
+    community via email to announce@apache.org
+    This must be sent from an @apache.org email address.
 </OL>
 
 <a name="site"></a>
@@ -247,21 +248,18 @@
     <LI>Build and test as described in the site/HOWTO document. 
     Note that the cgi page will not be active until it is on the server,
     so can't really be tested.</LI>
-<LI>Add the new files to the subversion repository.
-<pre>
+    <LI>Add the new files to the subversion repository.
+    <pre>
 svn add xdocs/releases/release-2.n.html 
 svn add docs/releases/release-2.n.html 
 svn add xocs/releases/release-2.n.cgi 
 svn add docs/releases/release-2.n.cgi 
-</pre>
-</LI>
+    </pre></LI>
     <LI>Set the svn properties svn:eol-style to native and svn:executable to true for the .cgi files.</LI>
 </OL>
 </LI>
-<LI>Change the link to RunRules on the <a href="http://db.apache.org/jdo/tck.html">TCK</a> page to link 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>Change the link to RunRules on the <a href="http://db.apache.org/jdo/tck.html">TCK</a> page to link 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>Add the javadoc for the release to the site.
 <OL>
     <LI>Make a new directory under site/docs for the release, e.g. api2.1. We'll call it <i>docsdir</i>.</LI>