openjpa-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From allee8...@apache.org
Subject svn commit: r1467041 - /openjpa/site/trunk/content/apache-nexus-release-process-(1.2.x-2.1.x).mdtext
Date Thu, 11 Apr 2013 18:50:42 GMT
Author: allee8285
Date: Thu Apr 11 18:50:42 2013
New Revision: 1467041

URL: http://svn.apache.org/r1467041
Log:
Fix typos and links.

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=1467041&r1=1467040&r2=1467041&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 Thu Apr 11
18:50:42 2013
@@ -99,7 +99,7 @@ created. If that doesn't help, try runni
 
         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]
+            2. verify signatures [Verifying release signatures](#verifySig)
 
     3. Once any failures or required updates have been committed to svn, rollback the release
prepare files -
     
@@ -131,7 +131,7 @@ Different arguments and steps are requir
         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.
+    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](http://openjpa.apache.org/release-setup.html)
for more information.
      
             $ mvn release:perform -Papache-release -Duser.name=<your-apache-uid>
 
@@ -154,7 +154,7 @@ Different arguments and steps are requir
     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>.
+        3. In Browser tab, navigate through the artifact tree and make sure that all javadoc,
sources, tests, jars, ... have .asc (GPG signature) and .md5 files. 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>.
     4. Close the nexus staging repo
         1. Select/check org.apache.openjpa-xxx and select Close.
 
@@ -162,8 +162,7 @@ Different arguments and steps are requir
     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
+                Subject: [VOTE] 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/
@@ -184,18 +183,14 @@ Different arguments and steps are requir
                 
                 Vote will be open for 72 hours.
                 
-                [ ](-.html)
-                +1  approve
-                [ ](-.html)
-                +0  no opinion
-                [ ](-.html)
-                -1  disapprove (and reason why)
+                [ ] +1  approve
+                [ ] +0  no opinion
+                [ ] -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
+                Subject: [DISCUSS] Apache OpenJPA 2.0.1 Release Candidate
                 
                 Discussion thread for vote on 2.0.1 release candidate, with SVN source tag
                 (rXXXXXX).
@@ -226,7 +221,7 @@ Different arguments and steps are requir
 
 11. Finalizing a release
     1. Release the staged nexus artifacts -
-        1. <https://repository.apache.org/index.html>
+        1. [https://repository.apache.org/index.html](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.
@@ -304,7 +299,7 @@ announcement.</span>
             $ 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>
+    1. [https://repository.apache.org/index.html](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.
@@ -319,7 +314,7 @@ announcement.</span>
 7. Spin another release candidate!
 
 
-<a name="ApacheNexusReleaseProcess(1.2.x-2.1.x)-{anchor:verifySig}Verifyingreleasesignatures"></a>
+<a name="verifySig"></a>
 # Verifying release signatures
 
 On unix platforms the following command can be executed -



Mime
View raw message