You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2026/08/10 16:32:38 UTC

(maven-site) branch hboutemy-patch-1 created (now 7377b293)

This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a change to branch hboutemy-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-site.git


      at 7377b293 split single huge cleanup list into groups of action

This branch includes the following new commits:

     new 7377b293 split single huge cleanup list into groups of action

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.



(maven-site) 01/01: split single huge cleanup list into groups of action

Posted by hb...@apache.org.
This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a commit to branch hboutemy-patch-1
in repository https://gitbox.apache.org/repos/asf/maven-site.git

commit 7377b29335408792fe85081c9089d8ef807701fa
Author: Hervé Boutemy <hb...@apache.org>
AuthorDate: Mon Aug 10 17:32:30 2026 +0100

    split single huge cleanup list into groups of action
    
    eases following the process
---
 .../markdown/developers/retirement-plan-plugins.md | 45 ++++++++++++----------
 1 file changed, 24 insertions(+), 21 deletions(-)

diff --git a/content/markdown/developers/retirement-plan-plugins.md b/content/markdown/developers/retirement-plan-plugins.md
index e71072ea..b61280a9 100644
--- a/content/markdown/developers/retirement-plan-plugins.md
+++ b/content/markdown/developers/retirement-plan-plugins.md
@@ -100,27 +100,30 @@ If the vote passes, make one final release of the plugin (with its own standard
 
 ## Step 3: Clean up after the release
 
-Everything that changes the repository has to be merged **before** INFRA archives it. An archived repository is read only, so anything left behind is frozen there permanently, and correcting it costs an unarchive/fix/re-archive round trip.
-
-1. Remove the `Jenkinsfile` from all branches. This will remove the project from the `maven-box` folder on https://ci-maven.apache.org/job/Maven/job/maven-box/
-2. Remove the `.github` directory from default branch. This will remove GitHub Actions
-   1. Deleting the directory stops new runs but leaves the old ones and their caches behind. Delete the workflow run history and the Actions caches as well, since they are frozen with the rest of the repository and serve no purpose once nothing can run again.
-3. Delete stale topic branches. Whatever survives is frozen by the archive, and a branch that still carries a `Jenkinsfile` can keep a build job alive.
-4. Update `.asf.yaml`:
-   1. Add " (RETIRED)" at the end of the project name.
-   2. Leave `homepage` pointing at the plugin's own site. That site stays published, so the link keeps working.
-   3. Remove `autolink_jira`. This stops the file claiming a Jira project that is being archived. It does not delete autolinks GitHub has already created. Ask INFRA for that.
-   4. Leave `features.issues` enabled. An archived repository keeps its issues readable, so disabling the feature would hide every report, including any migrated out of Jira.
-5. Replace the `README` with a short retirement notice. The file is otherwise a guide to forking the repository and opening pull requests, which is not actionable on a retired plugin. Keep it to what a visitor needs: that the plugin is retired, the last released version, a link to the plugin's site, and a link to the [mailing lists](https://maven.apache.org/mailing-lists.html) for questions.
-6. Ask INFRA to archive git repos (gitbox + github). Ask in the same ticket for the plugin's Jira project to be archived, if it has one.
-7. When relevant, update summary pages for [plugins](https://maven.apache.org/plugins/index.html) or [shared components](https://maven.apache.org/shared/index.html)
-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`
-   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), moving the entry from `default.xml` to `retired.xml` and removing the matching `<module>` from the aggregator pom. Both, or the aggregator build breaks for everyone who syncs the manifest.
-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. Remove the `.asc` and `.sha512` files as well as the archive itself. Leaving them behind publishes a signature for a file that no longer exists.
-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:
+Everything from step 1 that changes the Git repository has to be merged **before** INFRA archives it in step 2. An archived Git repository is read only, so anything left behind is frozen there permanently, and correcting it costs an unarchive/fix/re-archive round trip.
+
+1. Do Git cleanup
+   1. Remove the `Jenkinsfile` from all branches. This will remove the project from the `maven-box` folder on https://ci-maven.apache.org/job/Maven/job/maven-box/
+   2. Remove the `.github` directory from default branch. This will remove GitHub Actions
+      1. Deleting the directory stops new runs but leaves the old ones and their caches behind. Delete the workflow run history and the Actions caches as well, since they are frozen with the rest of the repository and serve no purpose once nothing can run again.
+   3. Delete stale topic branches. Whatever survives is frozen by the archive, and a branch that still carries a `Jenkinsfile` can keep a build job alive.
+   4. Update `.asf.yaml`:
+      1. Add " (RETIRED)" at the end of the project name.
+      2. Leave `homepage` pointing at the plugin's own site. That site stays published, so the link keeps working.
+      3. Remove `autolink_jira`. This stops the file claiming a Jira project that is being archived. It does not delete autolinks GitHub has already created. Ask INFRA for that.
+      4. Leave `features.issues` enabled. An archived repository keeps its issues readable, so disabling the feature would hide every report, including any migrated out of Jira.
+   5. Replace the `README` with a short retirement notice. The file is otherwise a guide to forking the repository and opening pull requests, which is not actionable on a retired plugin. Keep it to what a visitor needs: that the plugin is retired, the last released version, a link to the plugin's site, and a link to the [mailing lists](https://maven.apache.org/mailing-lists.html) for questions.
+2. **Ask INFRA to archive git repos (gitbox + github).**
+3. Cleanup references:
+   1. When relevant, update summary pages for [plugins](https://maven.apache.org/plugins/index.html) or [shared components](https://maven.apache.org/shared/index.html)
+   2. 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.
+   3. 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), moving the entry from `default.xml` to `retired.xml` and removing the matching `<module>` from the aggregator pom. Both, or the aggregator build breaks for everyone who syncs the manifest.
+4. Do some PMC tasks, or ask PMC to do:
+   1. 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. Remove the `.asc` and `.sha512` files as well as the archive itself. Leaving them behind publishes    a signature for a file that no longer exists.
+   2. Update board report. This needs to be done by PMC members.
+9. 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: announce@maven.apache.org, users@maven.apache.org