Author: buildbot
Date: Sat Jul 20 09:08:37 2013
New Revision: 870237
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 Sat Jul 20 09:08:37 2013
@@ -1 +1 @@
-1505101
+1505111
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
Sat Jul 20 09:08:37 2013
@@ -13,7 +13,7 @@
</style>
<link rel="stylesheet" href="../css/print.css" type="text/css"
media="print" />
<meta name="author" content="Dennis Lundberg" />
- <meta name="Date-Creation-yyyymmdd" content="20101230" />
+ <meta name="Date-Creation-yyyymmdd" content="20130720" />
<meta name="Date-Revision-yyyymmdd" content="20130720" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
@@ -240,14 +240,60 @@
<div id="contentBox">
<!-- Licensed to the Apache Software Foundation (ASF) under one
--><!-- or more contributor license agreements. See the NOTICE file --><!--
distributed with this work for additional information --><!-- regarding
copyright ownership. The ASF licenses this file --><!-- to you under the
Apache License, Version 2.0 (the --><!-- "License"); you may not use this file
except in compliance --><!-- with the License. You may obtain a copy of the
License at --><!-- --><!-- http://www.apache.org/licenses/LICENSE-2.0 --><!--
--><!-- Unless required by applicable law or agreed to in writing, --><!--
software distributed under the License is distributed on an --><!-- "AS IS"
BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY --><!-- KIND, either express or
implied. See the License for the --><!-- specific language governing
permissions and limitations --><!-- under the License. --><!-- NOTE: For help
with the syntax of this file, see: --><!--
http://maven.apache.org/doxia/references/apt-
format.html --><div class="section">
<h2>Retirement Plan for Plugins<a name="Retirement_Plan_for_Plugins"></a></h2>
-<ol style="list-style-type: decimal">
-<li>Propose a vote on the dev-list to retire a plugin. The vote should be open
for the standard 72 hours to allow people to voice their opinions. Send a cc to
the users-list. Standard Apache voting rules apply. Only PMC votes are binding.
+<div class="section">
+<h3>Decide to retire<a name="Decide_to_retire"></a></h3>
+<p>Propose a vote on the dev-list to retire a plugin. The vote should be open
for the standard 72 hours to allow people to voice their opinions. Send a cc to
the users-list. Standard Apache voting rules apply. Only PMC votes are
binding.</p>
<p>The vote must contain one or more options on how to retire the plugin.
There are multiple scenarios available. Here are a couple that have been
suggested:</p>
+<ol style="list-style-type: upper-alpha">
+<li>Move to our retired area in svn</li>
+<li>Move to another Apache project</li>
+<li>Move to mojo.codehaus.org, apache-extras.org or another forge</li></ol>
+<p>Here's a template for scenario A that can be used for the vote email:</p>
+<div class="source">
+<pre>To: "Maven Developers List" <[email protected]>
+Cc: "Maven Users List" <[email protected]>
+Subject: [VOTE] Retire Maven Foo Plugin
+
+Hi,
+
+A paragraph giving the reasons why the plugin should be retired. Make a note of
+how long it has been since the latest release.
+
+I therefor propose that we retire maven-foo-plugin.
+
+If this vote is successful I will make one final release of the plugin, making
+it clear on the plugin site that it has been retired. After that the source
code
+will be moved into the "retired" area in Subversion.
+
+The process for retiring a plugin is described here:
+http://maven.apache.org/developers/retirement-plan-plugins.html
+
+The vote is open for 72 hours.
+
+[ ] +1 Yes, it's about time
+[ ] -1 No, because...</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>
+<div class="section">
+<h3>Make the final release<a name="Make_the_final_release"></a></h3>
+<ol style="list-style-type: decimal">
+<li>Create an issue in JIRA with the issue type "Task" and the
summary "Retire this plugin", and schedule it for the final
release.</li>
+<li>Add the description "This is the final version of this plugin. It has
been retired." to the final version in JIRA.</li>
+<li>Add a prominent notice on the front page of the plugin's site, informing
that the plugin is retired. If the plugin is moved elsewhere, that should also
be added to the plugin's site. (Add notice templates)</li>
+<li>The final release must remove the "Source Repository" report
from the site, since the SCM URLs will be changed when the plugin is retired.
+<p>Currently this is not possible because all reports are inherited from the
parent. Here are two possible work-arounds, that unfortunately only work for
scenario A:</p>
<ul>
-<li>Move to retired area in svn</li>
-<li>Move to mojo.codehaus.org, apache-extras.org or another
forge</li></ul></li>
-<li>Make one final release of the plugin before it is retired. This allows us
to make a clean break. The final release must remove the "Source
Repository" report from the site, since the SCM URLs will be changed when
the plugin is retired. A prominent notice must be placed on the front page of
the plugin's site, informing that the plugin is retired. If the plugin is moved
elsewhere, that should also be posted on the plugin's site. The person who
wants to retire a plugin is the one who does the final release.</li>
-<li>Announce the fact that the plugin has been retired/moved on the
[email protected] and [email protected] mailing lists. Explain to people what they
should do if they would like to help with the continued development of the
plugin.</li></ol></div>
+<li>Change the SCM URL:s in the <tt>pom.xml</tt> of the checkout directory
before you deploy the site</li>
+<li>Specify the command line parameters <tt>anonymousConnection</tt>,
<tt>developerConnection</tt> and <tt>webAccessUrl</tt>, pointing to the new svn
location when you deploy the site</li></ul></li>
+<li>Go ahead with the standard release process, making sure that you follow
the exceptions mentioned above regarding the site deployment.</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>Put the JIRA project in read-only mode. (How to do this?)</li>
+<li>Update the plugins page, by moving Maven Foo Plugin to under the
"Retired" heading (does not exist yet). Remove the SVN and JIRA links
and add the date of retirement.</li>
+<li>Announce the fact that the plugin has been retired/moved on the
[email protected] and [email protected] mailing lists. Explain to people what they
should do if they would like to continue development of the
plugin.</li></ol><!-- Insert template for retirement email here --></div></div>
</div>
</div>
<div class="clear">
Modified: websites/staging/maven/trunk/content/maven-site-1.0-site.jar
==============================================================================
Binary files - no diff available.
