This is an automated email from the ASF dual-hosted git repository.
mbuenger 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 33219d1b Small update of retirement page
33219d1b is described below
commit 33219d1b80ca181d8769c9410bff9aaf38869340
Author: Matthias Bünger <buk...@users.noreply.github.com>
AuthorDate: Sat Feb 22 09:45:28 2025 +0100
Small update of retirement page
---
content/apt/developers/retirement-plan-plugins.apt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/content/apt/developers/retirement-plan-plugins.apt
b/content/apt/developers/retirement-plan-plugins.apt
index c104b75b..beabeae3 100644
--- a/content/apt/developers/retirement-plan-plugins.apt
+++ b/content/apt/developers/retirement-plan-plugins.apt
@@ -38,7 +38,7 @@ Retirement Plan for Plugins
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:
- [[A]] Move to our retired area in svn
+ [[A]] Repository will be archived (read only)
[[A]] Move to another Apache project
@@ -62,7 +62,7 @@ I therefore 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.
+repository will get archived, meaning it's read only in the future.
The process for retiring a plugin is described here:
https://maven.apache.org/developers/retirement-plan-plugins.html
