db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mcai...@apache.org
Subject svn commit: r707712 - /db/jdo/HowToReleaseJDO.html
Date Fri, 24 Oct 2008 18:45:56 GMT
Author: mcaisse
Date: Fri Oct 24 11:45:56 2008
New Revision: 707712

URL: http://svn.apache.org/viewvc?rev=707712&view=rev
Log:
Tweaks to release process.

Modified:
    db/jdo/HowToReleaseJDO.html

Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=707712&r1=707711&r2=707712&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Fri Oct 24 11:45:56 2008
@@ -113,15 +113,10 @@
 svn commit -m "Remove projects and files that are not being released"
 </pre>
 </LI>
-<LI>Update dependencies in projects to be released.
-
-<pre>
-For each project.xml in the branch:
-sed /-SNAPSHOT//gcd 
-popd
-</pre>
-
-If needed, update the dependency to JPOX in the tck20 project.xml.
+<LI>
+If needed, update the dependency to JPOX in the tck2 project.xml.
+</LI>
+<LI>
 If needed, apply patches from the trunk or branches to the new branch.
 </LI>
 <a name="version"></a>
@@ -129,11 +124,11 @@
 if these changes haven't been made previously.
 Check the following files:
 <DL>
-    <DT>trunk/project.properties
+    <DT>branches/<version>/project.properties
     <DD>Change value of currentVersion
-    <DT>trunk/README.html
+    <DT>branches/<version>/README.html
     <DD>File names and version references in the Overview section
-    <DT>trunk/JDO20.MF, api2/API2.MF, api2-legacy/API2.MF
+    <DT>branches/<version>/JDO20.MF, api2/API2.MF, api2-legacy/API2.MF
     <DD>Update Specification-Version and Bundle-Version
 </DL>
 </LI>
@@ -175,8 +170,9 @@
 <LI>Sign the artifacts. You must have a gpg key in order to perform this step.
 The sign-directory script is checked into jdo/bin. Edit this script to refer
 to your own environment (do not check it in).
-
+<pre>
 bin/sign-directory releases/2.n/dist/jdo2.<i>n</i>-rc<i>m</i>
+</pre>
 </LI>
 <LI>Push the artifacts to the staging area on the apache server.
 
@@ -197,7 +193,7 @@
     </LI>
     <LI>Send an announcement to test the release to the jdo-dev@db.apache.org alias.
If problems are found, fix and repeat.</LI>
     <LI>Send an announcement to vote on the release to the jdo-dev@db.apache.org alias.
-    The message subject line contains [VOTE].  Forward the [VOTE] message 
+The message subject line contains [VOTE].  Forward the [VOTE] message 
 to private@db.apache.org. Iterate until you get a successful vote. Mail the 
 results of the vote to jdo-dev@db.apache.org, cc: general@db.apache.org, and 
 include [VOTE] [RESULTS] in the subject line.
@@ -207,8 +203,8 @@
 
 <pre>
 ssh people.apache.org
-cp -r public_html/dist/db /www/www.apache.org
-cp -r public_html/dist/m1-ibiblio-rsync-repository/* /www/people.apache.org/repo/m1-ibiblio-rsync-repository
+cp -r public_html/jdo<i>version</i>/dist/db /www/www.apache.org/dist
+cp -r public_html/jdo<i>version</i>/dist/m1-ibiblio-rsync-repository/* /www/people.apache.org/repo/m1-ibiblio-rsync-repository
 </pre>
 NOTE!! Be sure that there is no slash at the end of the directory you are copying from; otherwise
the files will be put in the wrong target directory.
 </LI>
@@ -229,10 +225,13 @@
 <OL>
 <LI>Update the Apache JDO web site to point the downloads page to the release.
 <OL>
-    <LI>In site/docs/releases create release-2.n.html. Edit the release numbers</LI>
-    <LI>In site/docs/releases create release-2.n.cgi.  The .cgi file contents are identical
to the other .cgi files in the release directory; only the file name differs.</LI>
+    <LI>In site/xdocs/releases create release-2.n.xml. Edit the release numbers and
the link to the release notes. You will need to change the '&'s in the URL
+    to "&amp;amp;"</LI>
+    <LI>In site/xdocs/releases create release-2.n.cgi.  The .cgi file contents are
identical to the other .cgi files in the release directory; only the file name differs.</LI>
     <LI>Edit site/xdocs/downloads.xml to link to the new release page .cgi document.</LI>
-<LI>Build and test as described in the site/HOWTO document.  </LI>
+    <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>
 svn add xdocs/releases/release-2.n.html 
@@ -250,8 +249,8 @@
 </LI>
 <LI>Add the javadoc for the release to the site.
 <OL>
-    <LI>Make a new directory under site for the release, e.g. api2.1. Call it <i>docsdir</i>.</LI>
-    <LI>Copy the apidocs directory from the release branch target directory to <i>docsdir</i>.</LI>
+    <LI>Make a new directory under site/docs for the release, e.g. api2.1. We'll call
it <i>docsdir</i>.</LI>
+    <LI>Copy the apidocs directory from the release branch target/docs directory to
<i>docsdir</i>.</LI>
     <LI>Make a zip file of the apidocs tree and put it in <i>docsdir</i>.</LI>
     <LI>Do svn add on <i>docsdir</i>.</LI>
     <LI>Edit xdocs/javadoc.xml and add links to the new javadoc.</LI>



Mime
View raw message