This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/maven-site.git
The following commit(s) were added to refs/heads/master by this push:
new 6e56bdc9 adapt retirement to current situation
6e56bdc9 is described below
commit 6e56bdc9c2ebf1a1b61e822a6b86b67c6484cef0
Author: Hervé Boutemy <[email protected]>
AuthorDate: Sun May 24 10:16:05 2026 +0200
adapt retirement to current situation
no need for Jira step any more
---
.../markdown/developers/retirement-plan-plugins.md | 29 +++++++++-------------
1 file changed, 12 insertions(+), 17 deletions(-)
diff --git a/content/markdown/developers/retirement-plan-plugins.md
b/content/markdown/developers/retirement-plan-plugins.md
index 902af617..d096a578 100644
--- a/content/markdown/developers/retirement-plan-plugins.md
+++ b/content/markdown/developers/retirement-plan-plugins.md
@@ -19,7 +19,7 @@ under the License.
# Retirement Plan for Plugins
-## Decide to retire
+## Step 1: Decide to retire
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.
@@ -71,12 +71,13 @@ The vote has passed with the following result:
+1 (binding): <<list of names>>
+1 (non binding): <<list of names>>
-I will continue with the steps required to retire this plugin.
+I will continue with the steps required to retire this plugin:
+https://maven.apache.org/developers/retirement-plan-plugins.html
```
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 [our standard release
process](./release/maven-project-release-procedure.html).
-## Make the final release
+## Step 2: Make the final release
1. Create an issue in GitHub with the issue type "Task" and the summary
"Retire this plugin", and schedule it for the final release. If the plugin
includes a GitHub report in the generated site, you will need to close this
issue before you make the release.
2. Add the description "This is the final version of this plugin. It has been
retired." to the final version in GitHub.
@@ -84,7 +85,6 @@ If the vote passes, make one final release of the plugin
(with its own standard
```
Note: This plugin is retired. It is no longer maintained.
-
```
If the plugin is moved elsewhere, that should also be added to the plugin's
site. Suggested text:
@@ -92,29 +92,26 @@ If the vote passes, make one final release of the plugin
(with its own standard
```
Note: This plugin has retired from the Apache Maven project,
but has moved to the <Organization> <Project> project.
-
```
4. Add ` (RETIRED)` at the end of `<project>`/`<name>` in the plugin's
`pom.xml`. This will show up on every page of the generated site.
5. Go ahead with [the standard release
process](./release/maven-project-release-procedure.html), making sure that you
follow the exceptions mentioned above regarding the site deployment.
6. When updating the plugins page, move Maven Foo Plugin to under the
"Retired" heading. Remove the SVN/Github and Github Issues links and add the
date of retirement.
7. When updating the version in GitHub, do not add Y.Z+1 and make sure you
remove any future versions. This needs to be done by PMC members.
-## Clean up after the release
+## Step 3: Clean up after the release
1. Remove the `.Jenkinsfile` from all branches. This will remove the project
from https://builds.apache.org/job/maven-box/
2. Remove the `.github` directory from default branch. This will remove GitHub
Actions
-3. Ask INFRA for archive git repos (gitbox + github)
-4. Republish documentation, postfix project name with (RETIRED)
+3. Add " (RETIRED)" at the end of the project name in GitHub by updating
`.asf.yaml`
+4. Ask INFRA to archive git repos (gitbox + github)
5. When relevant update summary pages for
[plugins](https://maven.apache.org/plugins/index.html) or [shared
components](https://maven.apache.org/shared/index.html)
-6. Add " (RETIRED)" at the end of the project name in GitHub. This needs to be
done by PMC members.
-7. Put the JIRA project in read-only mode in case of standalone project (own
Jira key): apply Maven Retired Project Permissions Scheme. (Requires JIRA admin
karma: e.g. ask Brian Fox)
-8. Comment the [dist-tool
configuration](https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool.conf.html)
entry. Also comment the plugin's entry in the `GetPrerequisites.java` and
`ListBranchesReport` files.
-9. Remove from `Source Repository`
+6. Comment the [dist-tool
configuration](https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool.conf.html)
entry. Also comment the plugin's entry in the `GetPrerequisites.java` and
`ListBranchesReport` files.
+7. Remove from `Source Repository`
1. [https://maven.apache.org/scm.html](https://maven.apache.org/scm.html)
(includes the plantUML diagram)
2.
[https://github.com/apache/maven-sources](https://github.com/apache/maven-sources)
-10. Remove distribution from current [dist
area](https://dist.apache.org/repos/dist/release/maven/) (history remains
available in [archive](https://archive.apache.org/dist/maven/)). This needs to
be done by PMC members.
-11. Update board report. This needs to be done by PMC members.
-12. Announce the fact that the plugin has been retired/moved on the announce
and users mailing lists. Explain to people what they should do if they would
like to continue development of the plugin. Example for retirement email:
+8. Remove distribution from current [dist
area](https://dist.apache.org/repos/dist/release/maven/) (history remains
available in [archive](https://archive.apache.org/dist/maven/)). This needs to
be done by PMC members.
+9. Update board report. This needs to be done by PMC members.
+10. Announce the fact that the plugin has been retired/moved on the announce
and users mailing lists. Explain to people what they should do if they would
like to continue development of the plugin. Example for retirement email:
```
To: [email protected], [email protected]
@@ -132,6 +129,4 @@ If the vote passes, make one final release of the plugin
(with its own standard
You can write a mail to the users mailing list for that.
-The Apache Maven team
-
```
-
