Bukama commented on code in PR #1584: URL: https://github.com/apache/maven-site/pull/1584#discussion_r3294296720
########## content/markdown/developers/retirement-plan-plugins.md: ########## @@ -71,50 +71,48 @@ 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. 3. Add a prominent notice on the front page of the plugin's site, informing that the plugin is retired. Suggested text: ``` 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: ``` 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) -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` +3. Ask INFRA to archive git repos (gitbox + github) Review Comment: After re-reading. Shouldn't this be the last point on the last after all repository related things? Because when it's archived nothing can be changed on the repository anymore. So down to be before "When relevant, update summary..." -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
