You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by bu...@apache.org on 2014/03/30 17:40:27 UTC
svn commit: r904303 - in /websites/staging/maven/trunk/content: ./
developers/retirement-plan-plugins.html maven-site-1.0-site.jar
Author: buildbot
Date: Sun Mar 30 15:40:26 2014
New Revision: 904303
Log:
Staging update by buildbot for maven
Modified:
websites/staging/maven/trunk/content/ (props changed)
websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html
websites/staging/maven/trunk/content/maven-site-1.0-site.jar
Propchange: websites/staging/maven/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Sun Mar 30 15:40:26 2014
@@ -1 +1 @@
-1583144
+1583158
Modified: websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html
==============================================================================
--- websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html (original)
+++ websites/staging/maven/trunk/content/developers/retirement-plan-plugins.html Sun Mar 30 15:40:26 2014
@@ -284,7 +284,7 @@ The vote has passed with the following r
+1 (non binding): <<list of names>>
I will continue with the steps required to retire this plugin.</pre></div>
-<p>If the vote passes, make one final release of the plugin before it is retired. This allows us to make a clean break. The person who wants to retire a plugin is the one who does the final release. Below you will find the extra steps that you need to follow when retiring a plugin, in addition to our standard release process.</p></div>
+<p>If the vote passes, make one final release of the plugin (with its own standard 72h vote on source release) before it is retired. This allows us to make a clean break. The person who wants to retire a plugin is the one who does the final release. Below you will find the extra steps that you need to follow when retiring a plugin, in addition to <a href="./release/maven-project-release-procedure.html">our standard release process</a>.</p></div>
<div class="section">
<h3>Make the final release<a name="Make_the_final_release"></a></h3>
<ol style="list-style-type: decimal">
@@ -298,15 +298,15 @@ I will continue with the steps required
<pre>Note: This plugin has retired from the Apache Maven project,
but has moved to the <Organization> <Project> project.</pre></div></li>
<li>Add " (RETIRED)" at the end of <tt><project></tt>/<tt><name></tt> in the plugin's <tt>pom.xml</tt>. This will show up on every page of the generated site.</li>
-<li>Go ahead with the standard release process, making sure that you follow the exceptions mentioned above regarding the site deployment.</li>
+<li>Go ahead with <a href="./release/maven-project-release-procedure.html">the standard release process</a>, making sure that you follow the exceptions mentioned above regarding the site deployment.</li>
<li>When updating the plugins page, move Maven Foo Plugin to under the "Retired" heading. Remove the SVN and JIRA links and add the date of retirement.</li>
<li>When updating the version in JIRA, do not add Y.Z+1 and make sure you remove any future versions.</li></ol></div>
<div class="section">
<h3>Clean up after the release<a name="Clean_up_after_the_release"></a></h3>
<ol style="list-style-type: decimal">
<li>Remove the plugin from the <tt><modules></tt> section of the plugins aggregator POM.</li>
-<li>Remove any jobs from Continuous Integration servers like Jenkins. Plugins normally don't have separate jobs, but check anyway just to make sure.</li>
-<li>Move the source code in Subversion. Where to depends on which scenario was decided on.</li>
+<li>Remove any jobs from Continuous Integration servers like <a class="externalLink" href="http://builds.apache.org/">ASF Jenkins farm</a>. Plugins normally don't have separate jobs, but check anyway just to make sure.</li>
+<li>Move the source code in Subversion. <i>Where to</i> depends on which scenario was decided on.</li>
<li>Change the SCM URLs in the <tt>pom.xml</tt> to point to the new location.</li>
<li>Add " (RETIRED)" at the end of the project name in JIRA.</li>
<li>Put the JIRA project in read-only mode. (How to do this?)</li>
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.