svn commit: r1645368 - /maven/site/trunk/content/apt/developers/release/maven-core-release.apt

[jv...@apache.org]

Author: jvanzyl
Date: Sat Dec 13 22:43:10 2014
New Revision: 1645368

URL: http://svn.apache.org/r1645368
Log:
Add a small note about moving forward with versions in the event of a failed release.


Modified:
    maven/site/trunk/content/apt/developers/release/maven-core-release.apt

Modified: maven/site/trunk/content/apt/developers/release/maven-core-release.apt
URL: http://svn.apache.org/viewvc/maven/site/trunk/content/apt/developers/release/maven-core-release.apt?rev=1645368&r1=1645367&r2=1645368&view=diff
==============================================================================
--- maven/site/trunk/content/apt/developers/release/maven-core-release.apt (original)
+++ maven/site/trunk/content/apt/developers/release/maven-core-release.apt Sat Dec 13 22:43:10 2014
@@ -41,6 +41,9 @@ Releasing Maven
 
   []
 
+  Note that the policy for failed releases is to move forward with a new version. The tag that produced the failed released is
+  left in place for posterity. So if the release of, say, 3.2.4 fails then we move forward with 3.2.5.
+
 * Produce Release Candidates
 
   For non-alpha/beta releases, release candidates are produced before the actual
@@ -54,7 +57,7 @@ Releasing Maven
   procedure:
 
     * {{{./maven-project-release-procedure.html} Maven Project Common Release Procedure}}
-
+ 
   The version used should be the eventual version with -RC1, -RC2, etc. appended.
 
   After producing the RC, request that the developers test the release on the list.