db-jdo-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From an...@apache.org
Subject svn commit: r772355 - /db/jdo/HowToReleaseJDO.html
Date Wed, 06 May 2009 16:30:11 GMT
Author: andyj
Date: Wed May  6 16:30:11 2009
New Revision: 772355

URL: http://svn.apache.org/viewvc?rev=772355&view=rev
Log:
Some updates to include what not to check in, and updating version in project.xml of api2.
Also comments on Maven2 maven-metadata.xml

Modified:
    db/jdo/HowToReleaseJDO.html

Modified: db/jdo/HowToReleaseJDO.html
URL: http://svn.apache.org/viewvc/db/jdo/HowToReleaseJDO.html?rev=772355&r1=772354&r2=772355&view=diff
==============================================================================
--- db/jdo/HowToReleaseJDO.html (original)
+++ db/jdo/HowToReleaseJDO.html Wed May  6 16:30:11 2009
@@ -98,128 +98,144 @@
 <p>
 <OL>
     <LI>Create a branch from the trunk and increment the spec or major number.
-For example, create a 2.2 branch from the trunk.
-<pre>
+    For example, create a 2.2 branch from the trunk.
+    <pre>
 cd jdo
 svn copy https://svn.apache.org/repos/asf/db/jdo/trunk \
 https://svn.apache.org/repos/asf/db/jdo/branches/2.2
 </pre>
-</LI>
-<LI>Remove the projects and files that are not being released.
+    </LI>
 
+    <LI>Remove the projects and files that are not being released.
 <pre>
 pushd branches/2.n
 svn rm api11 btree fostore20 query20 runtime20 ri11 tck11 JDO11.MF 
 svn commit -m "Remove projects and files that are not being released"
 </pre>
-</LI>
-<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>
+    </LI>
+
+    <LI>If needed, update the dependency to DataNucleus 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>
-<LI>Update version numbers where necessary in projects to be released,
-if these changes haven't been made previously.
-Check the following files:
-<DL>
-    <DT>branches/<version>/project.properties
-    <DD>Change value of currentVersion
-    <DT>branches/<version>/README.html
-    <DD>File names and version references in the Overview section
-    <DT>branches/<version>/JDO20.MF, api2/API2.MF, api2-legacy/API2.MF
-    <DD>Update Specification-Version and Bundle-Version
-</DL>
-</LI>
-<LI>Copy the JNDI implementation jars (providerutil.jar and fscontext.jar) 
-to the branch lib/ext directory. This is needed to test the tck before 
-distributing it.
+    <LI>Update version numbers where necessary in projects to be released, if 
+    these changes haven't been made previously. Check the following files:
+        <DL>
+            <DT>branches/<version>/project.properties
+            <DD>Change value of currentVersion
+            <DT>branches/<version>/README.html
+            <DD>File names and version references in the Overview section
+            <DT>branches/<version>/JDO20.MF, api2/API2.MF, api2-legacy/API2.MF
+            <DD>Update Specification-Version and Bundle-Version
+            <DT>branches/<version>api2/project.xml
+            <DD>Update currentVersion
+        </DL>
+    </LI>
+
+    <LI>Update the details in branches/<version>/api2/m2_repo_maven_metadata.xml
+    to include the version being released.</LI>
+
+    <LI>Copy the JNDI implementation jars (providerutil.jar and fscontext.jar) 
+    to the branch lib/ext directory. This is needed to test the tck before 
+    distributing it.
 <pre>
 cp trunk/lib/ext/* branches/2.n/lib/ext
 </pre>
-</LI>
-<LI>Build the distribution. This creates .gz files and .zip files in the 
-target/distributions directory of each project. It also creates the .jar
-and .pom files.  It then copies the release artifacts to the 
-releases/2.n/dist directory. The dist directory is in a format that
-can be copied directly to the apache dist directory for distribution.
-It contains two subdirectories; db contains downloadable artifacts and java-repository contains
artifacts that are automatically pulled to maven repositories.
-
-Note: Failure possibly due to insufficient heap space was fixed by setting
-the environment variable MAVEN_OPTS="-Xmx1024m -Xms1024m -XX:MaxPermSize=512m"
+    <b>Do not check these in to SVN</b>
+    </LI>
 
+    <LI>Build the distribution. This creates .gz files and .zip files in the 
+    target/distributions directory of each project. It also creates the .jar
+    and .pom files.  It then copies the release artifacts to the 
+    releases/2.n/dist directory. The dist directory is in a format that
+    can be copied directly to the apache dist directory for distribution.
+    It contains two subdirectories; db contains downloadable artifacts and
+    java-repository contains artifacts that are automatically pulled to maven
+    repositories.
+    <I>Note: Failure possibly due to insufficient heap space was fixed by
+       setting the environment variable 
+       MAVEN_OPTS="-Xmx1024m -Xms1024m -XX:MaxPermSize=512m"</I>
 <pre>
 pushd branches/2.n
 maven tck2.default
 maven tck2.dist
 popd
 </pre>
-</LI>
-<LI>Test the release in the branch.
+    </LI>
 
+    <LI>Test the release in the branch.
 <pre>
 pushd branches/2.n/tck20
 maven installSchema
 maven runtck.jdori
 popd
 </pre>
+    Also run RAT on the release: http://code.google.com/p/arat/
+    </LI>
 
-Also run RAT on the release: http://code.google.com/p/arat/
-</LI>
-<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).
+    <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.
+    </LI>
 
+    <LI>Push the artifacts to the staging area on the apache server.
 <pre>
 scp -r releases/2.n/dist <i>username</i>@people.apache.org:~/public_html
 </pre>
+    </LI>
 
-</LI>
-<LI>
-ssh to people.apache.org and change to the public_html directory.
-Make sure that all the copied directories have executable permission. If not change the permission
for each:
-
+    <LI>ssh to people.apache.org and change to the public_html directory.
+    Make sure that all the copied directories have executable permission.
+    If not change the permission for each:
 <pre>
 chmod a+x <i>dir</i>
 </pre>
     </LI>
-    <LI>Test the release from the staging area. 
-    </LI>
+
+    <LI>Test the release from the staging area.</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 
-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.
-</LI>
-<LI>After testing and voting is complete, push the artifacts to the apache web.
-Mirrors automatically pick up Apache artifacts from /www/www.apache.org/dist.
 
+    <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 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.</LI>
+
+    <LI>After testing and voting is complete, push the artifacts to the 
+    Apache web. Mirrors automatically pick up Apache artifacts from 
+    /www/www.apache.org/dist.
 <pre>
 ssh people.apache.org
 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>
-<LI>Check the distribution into svn
+    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>
+    <LI>Copy the Maven 2 repository file to the location needed for it to be
+    pushed to IBiblio. <B>Check how to do this</B></LI>
+
+    <LI>Check the distribution into svn
 <pre>
 svn add releases/2.n
 svn commit "Create release 2.n" releases/2.n
 </pre>
-</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@general.apache.org
+    </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@general.apache.org
 </OL>
+
 <a name="site"></a>
 <h2>Site updates</h2>
 <OL>



Mime
View raw message