openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r1466713 - /openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Date Wed, 10 Apr 2013 22:18:03 GMT
Author: allee8285
Date: Wed Apr 10 22:18:02 2013
New Revision: 1466713

URL: http://svn.apache.org/r1466713
Log:
CMS commit to openjpa by allee8285

Modified:
    openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext

Modified: openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
URL: http://svn.apache.org/viewvc/openjpa/site/trunk/content/apache-nexus-release-process-%281.2.x-2.1.x%29.mdtext?rev=1466713&r1=1466712&r2=1466713&view=diff
==============================================================================
--- openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext (original)
+++ openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext Wed Apr 10
22:18:02 2013
@@ -1,323 +1,324 @@
-Title: Apache Nexus Release Process 1.2.x-2.1.x
-<a name="apache-nexus-release-process-(1.2.x-2.1.x)"></a>
-
-# Release Steps for OpenJPA 1.2.x - 2.1.x
-
-We're starting to move our builds over to using the Apache Nexus repository (repository.apache.org)
for releasing SNAPSHOT and release artifacts.
-More details on releasing artifacts and using Nexus can be found on the Maven website at
- <http://maven.apache.org/developers/release/apache-release.html>
-
-1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)
-    1. Increase the default Java heap available to Maven (required for Java SE 6)
-    
-            export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m" xx
-        
-    2. Use the latest Sun 1.6.0 JDK (1.5.0 for 1.2.x and 1.3.x)
-    3. Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
-    4. Make sure the [Release Setup](http://openjpa.apache.org/release-setup.html) steps
have been performed.
-        
-2. Prepare the source for release: 
-    1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes
this release version correctly.  Also, transition any Resolved issues to the Closed state.
-    2. Update the text files in a working copy of the openjpa-project subdir -
-        1. Update the CHANGES.txt based on the Text release reports from JIRA.
-            1. Choose the release from the "Versions" tab in the [releases page|https://issues.apache.org/jira/browse/OPENJPA/fixforversion/]
-            2. Click "Release Notes" link in upper right.
-        2. Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
-        3. Review and update README.txt and BUILDING.txt if needed.
-        4. Commit any changes back to svn - 
-        
-                $ svn commit -m "updating files for release"
-
-    1. Stage any Roadmap or Release landing pages on the wiki.
-    2. Verify the source has the required headers before trying to release.
-      
-            $ mvn apache-rat:check
-
-    1. Perform a full build with tests
-    
-            $ mvn clean install -Papache-release,docbook-profile,test-derby,bval
-
-    1. Run the JPA 1.0 TCK (for 1.x) and JPA 2.0 TCK (for 2.x) to verify the latest code
passes.
-    1. Perform a full build and deploy the SNAPSHOT artifacts
-    
-            $ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval
-DskipTests
-
-    1. Inspect the files in your local target directories to ensure:
-        * All jars and zips include:	LICENSE and NOTICE files
-        * The NOTICE files cover all third-party included files (like XSD schemas)
-        * The LICENSE files include any third-party licenses (like XSD schemas)
-        * The openjpa and openjpa-all jars include the right packages.
-        * The openjpa source and release distribution files have the right content.
-        * All jars/zips/poms have .asc (PGP signature) and md5 files
-    
-1. For new major releases (like 2.0.0 to 2.1.0)
-    1. Create a sub-branch from which to make the release. Releasing from a branch will allow
any cosmetic changes that need to be made for the release to be approved to be done without
preventing other more disruptive advances in the trunk from potentially causing problems with
the release. It also provides a future maintenance branch (like 2.0.x.)  A branch can be made
by running:
-    
-            $ mvn release:branch -DbranchName=2.0.x -Dusername=svn.user -Dpassword=svn.password
-
-1. Checkout a clean copy of the trunk/branch to release using command line svn.
-    1. Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse
throws off the rat:check processing and will get included in the source distribution.
-     
-            $ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
-
-        <span class="note">Make sure you use https:// protocol because the following
release:prepare step requires update to the svn repository.</span>
- 
-5. \(Optional\) Do a dry run of the release:prepare step.
-    1. The dry run will not commit any changes back to SVN and gives you the opportunity
to verify that the release process will complete as expected.  You will be prompted for the
following information :
-        1. Release version - take the default - (default 2.0.1) 
-        2. SCM release tag - *DO NOT TAKE THE DEFAULT* - (default openjpa-parent-2.0.1):
: 2.0.1
-        3. New development version - take the default - (default 2.0.2-SNAPSHOT) 
-        4. _optional_ if you have not specified a GPG passphrase in settings.xml you will
be prompted for it. 
-        
-                    $ mvn -Papache-release release:prepare -DdryRun=true
-        
-        <div class="note">
-     If you cancel a release:prepare before it updates the pom.xml versions,
-then use the *release:clean* goal to just remove the extra files that were
-created. If that doesn't help, try running *mvn clean*.</div>
-
-    2. Verify that the release process completed as expected
-        1. The release plugin will create pom.xml.tag files which contain the changes that
would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding
pom.xml file should be the version number.
-        2. If other formatting changes have been made you should review the changes and then
commit them -
-        
-                 $ svn commit -m "fixing formatting for release"
-
-        3. Assuming the .tag files look OK you may proceed and do any other validation you
feel necessary. The following list may be helpful 
-            1. Check release.properties and make sure that the scm properties have the right
version. Sometimes the scm location can be the previous version not the next version. *
-            2. verify signatures [Verifying release signatures|*verifySig]
-
-    3. Once any failures or required updates have been committed to svn, rollback the release
prepare files -
-    
-            $ mvn -Papache-release release:rollback
-
-6. Prepare the release
-    1. Run the "release:prepare" step for real this time.  You'll be prompted for the same
version information and optionally your GPG passphrase again.
-      
-            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
-                  [-Dusername=svn.user -Dpassword=svn.password](-dusername=svn.user--dpassword=svn.password.html)
\
-                  -DpreparationGoals="clean install"
-
-         <div class="note">
-Different arguments and steps are required as there are problems with the maven-jar-plugin
and maven-release-plugin when using the test-jar goal.  See <a href="http://jira.codehaus.org/browse/MJAR-68">http://jira.codehaus.org/browse/MJAR-68</a>
and <a href = "http://jira.codehaus.org/browse/MRELEASE-285">,http://jira.codehaus.org/browse/MRELEASE-285</a>.
-
-            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
-                  -DpreparationGoals="clean install"
-              ... Build failed....
-            $ mvn install -DskipTests
-            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
-                  -DpreparationGoals="clean install"
-
-        </div>
-
-7. Backup (zip or tar) your local release candidate directory in case you need to rollback
the release after the next step is performed.
-
-        cd ..
-        tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
-        cd 2.0.1-rc1
-
-8. Perform the release
-    1. This step will create a maven staging repository and site for use in testing and voting.
You will be prompted for your repository.apache.org and people.apache.org password several
times if you have not added server profiles to your settings.xml.	See [Release Setup] for
more information.
-     
-            $ mvn release:perform -Papache-release -Duser.name=<your_apache_uid>
-
-    2. The maven-release-plugin is configured with goals "deploy site site-deploy" and will
deploy the site files to a staging-site directory on people.apache.org.
-    
-9. Verify the release artifacts
-    1. Verify the HTML links in staging-site/index.html are correct
-        1. Login to people.apache.org
-        2. Edit public_html/openjpa/\[release\](release\.html) /staging-site/index.html and
updates the followings:
-
-                <a href="downloads/">Downloads</a>
-                  to
-                <a href="apache-openjpa/downloads/">Downloads</a>
-    
-                <a href="docs/index.html">docs/index.html</a>
-                  to
-                <a href="apache-openjpa/docs/index.html">docs/index.html</a>
-
-    2. Login to [Nexus](https://repository.apache.org/index.html)
-    3. Verify the staged artifacts in the nexus repo
-        1. Build Promotion --> Staging Repositories
-        2. Select/check org.apache.openjpa-xxx
-        3. In Browser tab, navigate through the artifact tree and make sure that all javadoc,
sources, tests, jars, ... have .asc (GPG signature) and .md5files. See [http://people.apache.org/~henkp/repo/faq.html](http://people.apache.org/~henkp/repo/faq.html)
and <http://www.apache.org/dev/release-signing.html/#openpgp-ascii-detach-sig>.
-    4. Close the nexus staging repo
-        1. Select/check org.apache.openjpa-xxx and select Close.
-
-10. Put the release candidate up for a vote
-    1. Create a VOTE email thread on dev@openjpa to record votes as replies, like -
-                
-                To: dev@
-                Subject: [VOTE](vote.html)
-                Apache OpenJPA 2.0.1 Release Candidate
-                I've created a 2.0.1 release candidate, with the following artifacts up for
a vote:
-                SVN source tag (rXXXXXX):
-                https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
-                        
-                Maven staging repo:
-                https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
-                
-                Source release:
-                https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/\
-                      org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
-                
-                Javadoc staging site:
-                http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
-                
-                PGP release keys (signed using D018E6B1):
-                https://svn.apache.org/repos/asf/openjpa/KEYS
-                
-                
-                Vote will be open for 72 hours.
-                
-                [ ](-.html)
-                +1  approve
-                [ ](-.html)
-                +0  no opinion
-                [ ](-.html)
-                -1  disapprove (and reason why)
-
-    2. Create a DISCUSS email thread on dev@ for any vote questions, like -
-    
-                To: dev@
-                Subject: [DISCUSS]
-                Apache OpenJPA 2.0.1 Release Candidate
-                
-                Discussion thread for vote on 2.0.1 release candidate, with SVN source tag
-                (rXXXXXX).
-                
-                For more information on the release process, checkout -
-                http://www.apache.org/dev/release.html
-                http://incubator.apache.org/guides/releasemanagement.html
-                
-                Some of the things to check before voting are:
-                - does "mvn apache-rat:check" pass on the source
-                - can you build the contents of source-release.zip and svn tag
-                - do all of the staged jars/zips contain the required LICENSE and NOTICE
-                files
-                - are all of the staged jars signed and the signature verifiable
-                - is the signing key in the project's KEYS file and on a public server
-                - does the release pass the TCK
-
-    3. Perform a review of the release and cast your vote. See the following for more details
on Apache releases -
-        1. [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
-        1. [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
-    4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually
a good idea to rollback the release if a -1 vote is received. See - [*Recovering from a vetoed
release](*recovering-from-a-vetoed-release.html)
-    5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes
and no -1 votes, then post the results to the vote thread by -
-        1. Reply to the initial email and prepend to the original subject -
- 
-                [RESULTS]
-        
-        2. Include a list of everyone who voted +1, 0 or -1.
-
-11. Finalizing a release
-    1. Release the staged nexus artifacts -
-        1. <https://repository.apache.org/index.html>
-        2. Build Promotion --> Staging Repositories
-        3. Select/check org.apache.openjpa-xxx and select Release.
-    2. Copy the staged site over to the openjpa/builds location on people.apache.org.
-        1. ssh to people.apache.org
-
-                $ mkdir /www/openjpa.apache.org/builds/2.0.1
-                $ cp -r ~/public_html/openjpa/2.0.1/staging-site/* /www/openjpa.apache.org/builds/2.0.1/
-                $ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
-
-        2. Update the assemblies in the Downloads directory.  For this, we'll just wget copies
of the released assemblies with their signatures and hashes from the Apache repo:
-        
-                $ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
-                wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/\
-                      org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
-                wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/\
-                      org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
-
-            Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files above.
-
-        3. copy the RELEASE-NOTES.html to the proper location
-
-                $ cd ...../2.0.1-rc1/
-                $ scp openjpa-project/RELEASE-NOTES.html allee8285@people.apache.org:\
-                      /www/openjpa.apache.org/builds/2.0.1/apache-openjpa
-
-        4. verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly
by comparing it to a previous release. 
-
-                $ rm /www/openjpa.apache.org/docs/latest
-                $ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest

-
-    3. Copy the distribution artifacts over to the distribution area.
-
-            mkdir /www/www.apache.org/dist/openjpa/2.0.1
-            cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
-            chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
-            chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
-
-        1. Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1
you would remove 2.0.0.  Verify that the release being removed is in the distribution archives
before removing.
-
-                $ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
-                $ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
-
-    4. Update the [JIRA Releases](https://issues.apache.org/jira/browse/OPENJPA) page to
mark the version as "released", and set the date to the date that the release was approved.
You may also need to make a new release entry for the next release.
-    
-12. Update wiki pages
-    1. After the distribution and build files have been mirrored out to the external sites
(takes about an hour), update the [Downloads](/downloads.html) and [Documentation](/documentation.html)
pages with the new release.
-    2. Make a blog announcement on the OpenJPA wiki. 
-        1. FIX ME!
-
-13. Announcing the release
-    1. FIX MEEEE After the Maven mirrors have had time to update (24 hours to be on the safe
side) and the wiki updates have been exported and mirrored to the external website, then it's
time to announce the release.  Make an announcement about the release on the dev@, user@ and
[mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html*foundation-announce]
-)
-
-        <span class="note">
-Make sure you send the announcement to announce@apache.org from your
-user@apache.org. This can be achieved using gmail by setting the "From"
-field to user@apche.org instead of user@gmail.com when sending the
-announcement.</span>
-    
- 
-# Recovering from a vetoed release
-1. Reply to the initial vote email and prepend to the original subject -
-
-        [CANCELED]
-
-2. Rollback the version upgrades in trunk by either -
-    1. Restore the 2.0.1-rc1.tar.gz and run
-    
-            $ mvn -Papache-release release:rollback
-
-    2. Manually revert the versions in trunk to the prior version and commit
-
-3. Delete the svn tag created by the release:perform step -
-
-            $ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release
attempt"
-   
-4. Drop the nexus staging repo
-    1. <https://repository.apache.org/index.html>
-    2. Enterprise --> Staging
-    3. Staging tab --> Name column --> org.apache.openjpa
-    4. Right click on the closed staging repo (org.apache.openjpa-XXX) and select Drop.
-        
-5. Remove the staged site
-
-        $ ssh ${user.name}@people.apache.org 
-        $ cd ~/public_html/openjpa
-        $ rm -fr ${project.version}
-
-6. Make the required updates that caused the vote to be canceled
-7. Spin another release candidate!
-
-
-<a name="ApacheNexusReleaseProcess(1.2.x-2.1.x)-{anchor:verifySig}Verifyingreleasesignatures"></a>
-# Verifying release signatures
-
-On unix platforms the following command can be executed -
-
-    for file in `find . -type f -iname '*.asc'`
-    do
-        gpg --verify ${file} 
-    done
-
-    
-You'll need to look at the output to ensure it contains only good
-signatures -
-
-    gpg: Good signature from ...
-    gpg: Signature made ...
-  
-  
+Title: Apache Nexus Release Process 1.2.x-2.1.x
+
+<a name="apache-nexus-release-process-(1.2.x-2.1.x)"></a>
+
+# Release Steps for OpenJPA 1.2.x - 2.1.x
+
+We're starting to move our builds over to using the Apache Nexus repository (repository.apache.org)
for releasing SNAPSHOT and release artifacts.
+More details on releasing artifacts and using Nexus can be found on the Maven website at
- <http://maven.apache.org/developers/release/apache-release.html>
+
+1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)
+    1. Increase the default Java heap available to Maven (required for Java SE 6)
+    
+            export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=512m"
+        
+    2. Use the latest Sun 1.6.0 JDK (1.5.0 for 1.2.x and 1.3.x)
+    3. Use Maven 2.2.1 or later (2.2.1 is required for release signing fixes)
+    4. Make sure the [Release Setup](http://openjpa.apache.org/release-setup.html) steps
have been performed.
+        
+2. Prepare the source for release: 
+    1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes
this release version correctly.  Also, transition any Resolved issues to the Closed state.
+    2. Update the text files in a working copy of the openjpa-project subdir -
+        1. Update the CHANGES.txt based on the Text release reports from JIRA.
+            1. Choose the release from the "Versions" tab in the [releases page](https://issues.apache.org/jira/browse/OPENJPA/fixforversion/)
+            2. Click "Release Notes" link in upper right.
+        2. Update the RELEASE-NOTES.html based on the HTML release reports from JIRA.
+        3. Review and update README.txt, CHANGES.txt, BUILDING.txt and NOTICE if needed.
+        4. Commit any changes back to svn - 
+        
+                $ svn commit -m "Updating files for release."
+
+    1. Stage any Roadmap or Release landing pages on the wiki.
+    2. Verify the source has the required headers before trying to release.
+      
+            $ mvn apache-rat:check
+
+    1. Perform a full build with tests
+    
+            $ mvn clean install -Papache-release,docbook-profile,test-derby,bval
+
+    1. Run the JPA 1.0 TCK (for 1.x) and JPA 2.0 TCK (for 2.x) to verify the latest code
passes.
+    1. Perform a full build and deploy the SNAPSHOT artifacts
+    
+            $ mvn clean deploy site site-deploy -Papache-release,docbook-profile,test-derby,bval
-DskipTests
+
+    1. Inspect the files in your local target directories to ensure:
+        * All jars and zips include:	LICENSE and NOTICE files
+        * The NOTICE files cover all third-party included files (like XSD schemas)
+        * The LICENSE files include any third-party licenses (like XSD schemas)
+        * The openjpa and openjpa-all jars include the right packages.
+        * The openjpa source and release distribution files have the right content.
+        * All jars/zips/poms have .asc (PGP signature) and md5 files
+    
+1. For new major releases (like 2.0.0 to 2.1.0)
+    1. Create a sub-branch from which to make the release. Releasing from a branch will allow
any cosmetic changes that need to be made for the release to be approved to be done without
preventing other more disruptive advances in the trunk from potentially causing problems with
the release. It also provides a future maintenance branch (like 2.0.x.)  A branch can be made
by running:
+    
+            $ mvn release:branch -DbranchName=2.0.x -Dusername=svn.user -Dpassword=svn.password
+
+1. Checkout a clean copy of the trunk/branch to release using command line svn.
+    1. Do not use Eclipse to do the checkout. The extra dot (.) files created by Eclipse
throws off the rat:check processing and will get included in the source distribution.
+     
+            $ svn checkout https://svn.apache.org/repos/asf/openjpa/branches/2.0.x/ 2.0.1-rc1/
+
+        <span class="note">Make sure you use https:// protocol because the following
release:prepare step requires update to the svn repository.</span>
+ 
+5. \(Optional\) Do a dry run of the release:prepare step.
+    1. The dry run will not commit any changes back to SVN and gives you the opportunity
to verify that the release process will complete as expected.  You will be prompted for the
following information :
+        1. Release version - take the default - (default 2.0.1) 
+        2. SCM release tag - *DO NOT TAKE THE DEFAULT* - (default openjpa-parent-2.0.1):
: 2.0.1
+        3. New development version - take the default - (default 2.0.2-SNAPSHOT) 
+        4. _optional_ if you have not specified a GPG passphrase in settings.xml you will
be prompted for it. 
+        
+                    $ mvn -Papache-release release:prepare -DdryRun=true
+        
+        <div class="note">
+     If you cancel a release:prepare before it updates the pom.xml versions,
+then use the *release:clean* goal to just remove the extra files that were
+created. If that doesn't help, try running *mvn clean*.</div>
+
+    2. Verify that the release process completed as expected
+        1. The release plugin will create pom.xml.tag files which contain the changes that
would have been committed to SVN. The only differences between pom.xml.tag and it's corresponding
pom.xml file should be the version number.
+        2. If other formatting changes have been made you should review the changes and then
commit them -
+        
+                 $ svn commit -m "fixing formatting for release"
+
+        3. Assuming the .tag files look OK you may proceed and do any other validation you
feel necessary. The following list may be helpful 
+            1. Check release.properties and make sure that the scm properties have the right
version. Sometimes the scm location can be the previous version not the next version. *
+            2. verify signatures [Verifying release signatures|*verifySig]
+
+    3. Once any failures or required updates have been committed to svn, rollback the release
prepare files -
+    
+            $ mvn -Papache-release release:rollback
+
+6. Prepare the release
+    1. Run the "release:prepare" step for real this time.  You'll be prompted for the same
version information and optionally your GPG passphrase again.
+      
+            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
+                  -DpreparationGoals="clean install" \
+                  [-Dusername=svn.user -Dpassword=svn.password]
+
+         <div class="note">
+Different arguments and steps are required as there are problems with the maven-jar-plugin
and maven-release-plugin when using the test-jar goal.  See <a href="http://jira.codehaus.org/browse/MJAR-68">http://jira.codehaus.org/browse/MJAR-68</a>
and <a href = "http://jira.codehaus.org/browse/MRELEASE-285">,http://jira.codehaus.org/browse/MRELEASE-285</a>.
+
+            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
+                  -DpreparationGoals="clean install"
+              ... Build failed....
+            $ mvn install -DskipTests
+            $ mvn release:prepare -Papache-release,docbook-profile,test-derbymem,bval -DskipTests
\
+                  -DpreparationGoals="clean install"
+
+        </div>
+
+7. Backup (zip or tar) your local release candidate directory in case you need to rollback
the release after the next step is performed.
+
+        cd ..
+        tar -czf 2.0.1-rc1-preRelease.tar.gz 2.0.1-rc1/
+        cd 2.0.1-rc1
+
+8. Perform the release
+    1. This step will create a maven staging repository and site for use in testing and voting.
You will be prompted for your repository.apache.org and people.apache.org password several
times if you have not added server profiles to your settings.xml.	See [Release Setup] for
more information.
+     
+            $ mvn release:perform -Papache-release -Duser.name=<your-apache-uid>
+
+    2. The maven-release-plugin is configured with goals "deploy site site-deploy" and will
deploy the site files to a staging-site directory on people.apache.org.
+    
+9. Verify the release artifacts
+    1. Verify the HTML links in staging-site/index.html are correct
+        1. Login to people.apache.org
+        2. Edit public_html/openjpa/\[release\]/staging-site/index.html and updates the followings:
+
+                <a href="downloads/">Downloads</a>
+                  to
+                <a href="apache-openjpa/downloads/">Downloads</a>
+    
+                <a href="docs/index.html">docs/index.html</a>
+                  to
+                <a href="apache-openjpa/docs/index.html">docs/index.html</a>
+
+    2. Login to [Nexus](https://repository.apache.org/index.html)
+    3. Verify the staged artifacts in the nexus repo
+        1. Build Promotion --> Staging Repositories
+        2. Select/check org.apache.openjpa-xxx
+        3. In Browser tab, navigate through the artifact tree and make sure that all javadoc,
sources, tests, jars, ... have .asc (GPG signature) and .md5files. See [http://people.apache.org/~henkp/repo/faq.html](http://people.apache.org/~henkp/repo/faq.html)
and <http://www.apache.org/dev/release-signing.html/#openpgp-ascii-detach-sig>.
+    4. Close the nexus staging repo
+        1. Select/check org.apache.openjpa-xxx and select Close.
+
+10. Put the release candidate up for a vote
+    1. Create a VOTE email thread on dev@openjpa to record votes as replies, like -
+                
+                To: dev@
+                Subject: [VOTE](vote.html)
+                Apache OpenJPA 2.0.1 Release Candidate
+                I've created a 2.0.1 release candidate, with the following artifacts up for
a vote:
+                SVN source tag (rXXXXXX):
+                https://svn.apache.org/repos/asf/openjpa/tags/2.0.1/
+                        
+                Maven staging repo:
+                https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/
+                
+                Source release:
+                https://repository.apache.org/content/repositories/orgapacheopenjpa-XXX/\
+                      org/apache/openjpa/openjpa-parent/2.0.1/openjpa-parent-2.0.1-source-release.zip
+                
+                Javadoc staging site:
+                http://people.apache.org/~dwoods/openjpa/2.0.1/staging-site/apidocs/
+                
+                PGP release keys (signed using D018E6B1):
+                https://svn.apache.org/repos/asf/openjpa/KEYS
+                
+                
+                Vote will be open for 72 hours.
+                
+                [ ](-.html)
+                +1  approve
+                [ ](-.html)
+                +0  no opinion
+                [ ](-.html)
+                -1  disapprove (and reason why)
+
+    2. Create a DISCUSS email thread on dev@ for any vote questions, like -
+    
+                To: dev@
+                Subject: [DISCUSS]
+                Apache OpenJPA 2.0.1 Release Candidate
+                
+                Discussion thread for vote on 2.0.1 release candidate, with SVN source tag
+                (rXXXXXX).
+                
+                For more information on the release process, checkout -
+                http://www.apache.org/dev/release.html
+                http://incubator.apache.org/guides/releasemanagement.html
+                
+                Some of the things to check before voting are:
+                - does "mvn apache-rat:check" pass on the source
+                - can you build the contents of source-release.zip and svn tag
+                - do all of the staged jars/zips contain the required LICENSE and NOTICE
+                files
+                - are all of the staged jars signed and the signature verifiable
+                - is the signing key in the project's KEYS file and on a public server
+                - does the release pass the TCK
+
+    3. Perform a review of the release and cast your vote. See the following for more details
on Apache releases -
+        1. [http://www.apache.org/dev/release.html](http://www.apache.org/dev/release.html)
+        1. [http://incubator.apache.org/guides/releasemanagement.html](http://incubator.apache.org/guides/releasemanagement.html)
+    4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually
a good idea to rollback the release if a -1 vote is received. See - [*Recovering from a vetoed
release](*recovering-from-a-vetoed-release.html)
+    5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes
and no -1 votes, then post the results to the vote thread by -
+        1. Reply to the initial email and prepend to the original subject -
+ 
+                [RESULTS]
+        
+        2. Include a list of everyone who voted +1, 0 or -1.
+
+11. Finalizing a release
+    1. Release the staged nexus artifacts -
+        1. <https://repository.apache.org/index.html>
+        2. Build Promotion --> Staging Repositories
+        3. Select/check org.apache.openjpa-xxx and select Release.
+    2. Copy the staged site over to the openjpa/builds location on people.apache.org.
+        1. ssh to people.apache.org
+
+                $ mkdir /www/openjpa.apache.org/builds/2.0.1
+                $ cp -r ~/public_html/openjpa/2.0.1/staging-site/* /www/openjpa.apache.org/builds/2.0.1/
+                $ chmod -R g+w /www/openjpa.apache.org/builds/2.0.1
+
+        2. Update the assemblies in the Downloads directory.  For this, we'll just wget copies
of the released assemblies with their signatures and hashes from the Apache repo:
+        
+                $ cd /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads
+                wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/\
+                      org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-source.zip
+                wget [--no-check-certificate] https://repository.apache.org/content/repositories/releases/\
+                      org/apache/openjpa/apache-openjpa/2.0.1/apache-openjpa-2.0.1-binary.zip
+
+            Along with the *.zip.asc, *.zip.md5 and *.zip.sha1 for both ZIP files above.
+
+        3. copy the RELEASE-NOTES.html to the proper location
+
+                $ cd ...../2.0.1-rc1/
+                $ scp openjpa-project/RELEASE-NOTES.html allee8285@people.apache.org:\
+                      /www/openjpa.apache.org/builds/2.0.1/apache-openjpa
+
+        4. verify that /www/openjpa.apache.org/builds/2.0.1/docs/manual is populated correctly
by comparing it to a previous release. 
+
+                $ rm /www/openjpa.apache.org/docs/latest
+                $ ln -fvs ../builds/2.0.1/apache-openjpa/docs/ /www/openjpa.apache.org/docs/latest

+
+    3. Copy the distribution artifacts over to the distribution area.
+
+            mkdir /www/www.apache.org/dist/openjpa/2.0.1
+            cp /www/openjpa.apache.org/builds/2.0.1/apache-openjpa/downloads/* /www/www.apache.org/dist/openjpa/2.0.1/
+            chgrp -R openjpa /www/www.apache.org/dist/openjpa/2.0.1
+            chmod -R g+w /www/www.apache.org/dist/openjpa/2.0.1
+
+        1. Optional: Remove the previous version from /dist. Ie if you're publishing 2.0.1
you would remove 2.0.0.  Verify that the release being removed is in the distribution archives
before removing.
+
+                $ ls -la /www/archive.apache.org/dist/openjpa/2.0.0/
+                $ rm -rf /www/openjpa.apache.org/dist/openjpa/2.0.0
+
+    4. Update the [JIRA Releases](https://issues.apache.org/jira/browse/OPENJPA) page to
mark the version as "released", and set the date to the date that the release was approved.
You may also need to make a new release entry for the next release.
+    
+12. Update wiki pages
+    1. After the distribution and build files have been mirrored out to the external sites
(takes about an hour), update the [Downloads](/downloads.html) and [Documentation](/documentation.html)
pages with the new release.
+    2. Make a blog announcement on the OpenJPA wiki. 
+        1. FIX ME!
+
+13. Announcing the release
+    1. FIX MEEEE After the Maven mirrors have had time to update (24 hours to be on the safe
side) and the wiki updates have been exported and mirrored to the external website, then it's
time to announce the release.  Make an announcement about the release on the dev@, user@ and
[mailto:announce@apache.org] list as per [the Apache Announcement Mailing Lists page|http://www.apache.org/foundation/mailinglists.html*foundation-announce]
+)
+
+        <span class="note">
+Make sure you send the announcement to announce@apache.org from your
+user@apache.org. This can be achieved using gmail by setting the "From"
+field to user@apche.org instead of user@gmail.com when sending the
+announcement.</span>
+    
+ 
+# Recovering from a vetoed release
+1. Reply to the initial vote email and prepend to the original subject -
+
+        [CANCELED]
+
+2. Rollback the version upgrades in trunk by either -
+    1. Restore the 2.0.1-rc1.tar.gz and run
+    
+            $ mvn -Papache-release release:rollback
+
+    2. Manually revert the versions in trunk to the prior version and commit
+
+3. Delete the svn tag created by the release:perform step -
+
+            $ svn del https://svn.apache.org/repos/asf/openjpa/tags/2.0.1 -m "rollback release
attempt"
+   
+4. Drop the nexus staging repo
+    1. <https://repository.apache.org/index.html>
+    2. Enterprise --> Staging
+    3. Staging tab --> Name column --> org.apache.openjpa
+    4. Right click on the closed staging repo (org.apache.openjpa-XXX) and select Drop.
+        
+5. Remove the staged site
+
+        $ ssh ${user.name}@people.apache.org 
+        $ cd ~/public_html/openjpa
+        $ rm -fr ${project.version}
+
+6. Make the required updates that caused the vote to be canceled
+7. Spin another release candidate!
+
+
+<a name="ApacheNexusReleaseProcess(1.2.x-2.1.x)-{anchor:verifySig}Verifyingreleasesignatures"></a>
+# Verifying release signatures
+
+On unix platforms the following command can be executed -
+
+    for file in `find . -type f -iname '*.asc'`
+    do
+        gpg --verify ${file} 
+    done
+
+    
+You'll need to look at the output to ensure it contains only good
+signatures -
+
+    gpg: Good signature from ...
+    gpg: Signature made ...
+  
+  



Mime
View raw message