svn commit: r1762627 - /incubator/public/trunk/content/guides/releasemanagement.xml

[ma...@apache.org]

Author: markt
Date: Wed Sep 28 09:42:49 2016
New Revision: 1762627

URL: http://svn.apache.org/viewvc?rev=1762627&view=rev
Log:
Add Git+Maven info
Add links to release process examples

Modified:
    incubator/public/trunk/content/guides/releasemanagement.xml

Modified: incubator/public/trunk/content/guides/releasemanagement.xml
URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/releasemanagement.xml?rev=1762627&r1=1762626&r2=1762627&view=diff
==============================================================================
--- incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] (original)
+++ incubator/public/trunk/content/guides/releasemanagement.xml [utf-8] Wed Sep 28 09:42:49 2016
@@ -1130,6 +1130,24 @@ This ensure that all the source for the
 changes then the release will no longer be complete reproducible.
         	</p>
         </section>
+        <section id='best-practices-git-maven'><title>Git with Maven Best Practices</title>
+            <p>
+First and important: configure the maven-release-plugin to operate 'locally'
+<a href="https://github.com/apache/deltaspike/blob/master/pom.xml#L123">https://github.com/apache/deltaspike/blob/master/pom.xml#L123</a>
+            </p>
+            <p>
+The important parts are:
+            </p>
+<source>
+&lt;pushChanges&gt;false&lt;/pushChanges&gt;
+&lt;localCheckout&gt;true&lt;/localCheckout&gt;
+</source>
+            <p>
+This will configure maven to NOT push you changes upstream to the repo mentioned in the SCM section, but only keep it local.
+And during the release:perform this will also pick up the tag from local.
+That means you need to push it to e.g. github yourself. 
+            </p>
+        </section>
         <section id='best-practice-reproducability'><title>Reproducibility</title>
         	<p>
 It is important that any release can be reproduced from the source at any time in the future. 
@@ -1146,6 +1164,19 @@ is not mature enough for a full Apache r
 The requirements of the build should be fully documented. The versions of tools 
 and platforms used to build the release should be noted.
         	</p>
+            <p>
+The following are examples of how existing ASF projects have documented their release
+process.
+          </p>
+          <ul>
+            <li><a href="https://sling.apache.org/documentation/development/release-management.html">Apache Sling</a></li>
+            <li><a href="https://cwiki.apache.org/confluence/display/TOMCAT/Building+the+Tomcat+Native+Connector+binaries+for+Windows">Apache Tomcat Native Connectors</a></li>
+            <li><a href="https://deltaspike.apache.org/steps_for_a_release.html">Apache DeltaSpike</a></li>
+            <li><a href="https://github.com/apache/wicket/blob/master/release.sh">Apache Wicket release script</a></li>
+            <li><a href="https://s.apache.org/accumulo-build-script">Apache Accumulo build script</a></li>
+            <li><a href="https://cwiki.apache.org/confluence/display/GEODE/Release+Steps">Apache Geode release process</a></li>
+          </ul>
+              
         </section>
         <section id='best-practice-release-as-advertising'><title>Release As Advertising</title>
         	<p>



---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org