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

[cu...@apache.org]

Author: curtisr7
Date: Wed Nov 21 13:48:12 2012
New Revision: 1412094

URL: http://svn.apache.org/viewvc?rev=1412094&view=rev
Log:
update apache-nexus-release-process wiki

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=1412094&r1=1412093&r2=1412094&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 Nov 21 13:48:12 2012
@@ -67,8 +67,10 @@ More details on releasing artifacts and 
         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. 
-<code><pre>     $ mvn -Papache-release release:prepare -DdryRun=true</code></pre>
-<div class="note">
+        
+                    $ 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>
@@ -124,7 +126,7 @@ Different arguments and steps are requir
         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/"&gt;Downloads/&lt;a&gt;
+                <a href="downloads/">Downloads</a>
                   to
                 <a href="apache-openjpa/downloads/">Downloads</a>
     
@@ -271,8 +273,8 @@ announcement.</span>
  
 # Recovering from a vetoed release
 1. Reply to the initial vote email and prepend to the original subject -
- 
-    [CANCELED]
+
+        [CANCELED]
 
 2. Rollback the version upgrades in trunk by either -
     1. Restore the 2.0.1-rc1.tar.gz and run
@@ -293,9 +295,9 @@ announcement.</span>
         
 5. Remove the staged site
 
-    $ ssh ${user.name}@people.apache.org 
-    $ cd ~/public_html/openjpa
-    $ rm -fr ${project.version}
+        $ 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!