svn commit: r1767077 - /bval/cms-site/trunk/content/release-process.mdtext

[mb...@apache.org]

Author: mbenson
Date: Fri Oct 28 21:11:13 2016
New Revision: 1767077

URL: http://svn.apache.org/viewvc?rev=1767077&view=rev
Log:
CMS commit to bval by mbenson

Modified:
    bval/cms-site/trunk/content/release-process.mdtext

Modified: bval/cms-site/trunk/content/release-process.mdtext
URL: http://svn.apache.org/viewvc/bval/cms-site/trunk/content/release-process.mdtext?rev=1767077&r1=1767076&r2=1767077&view=diff
==============================================================================
--- bval/cms-site/trunk/content/release-process.mdtext (original)
+++ bval/cms-site/trunk/content/release-process.mdtext Fri Oct 28 21:11:13 2016
@@ -17,7 +17,7 @@ releases)
             export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=256m"
 
     1. Use the latest Sun 1.6.0 JDK
-    1. Use Maven 2.2.1 or later (required for release signing fixes)
+    1. Use Maven 3.2.1 or later
     1. Make sure the [Release Setup][] steps have been performed.
 
 1. Prepare the source for release: 
@@ -33,7 +33,7 @@ releases)
                 svn commit -m "updating files for release"
 
     1. Stage any Roadmap or Release landing pages on the wiki.
-    1. Use `mvn rat:check` to verify the source has the required headers before
+    1. Use `mvn apache-rat:check` to verify the source has the required headers before
        trying to release.
     1. Perform a full build and deploy the SNAPSHOT artifacts: