slachiewicz opened a new pull request, #67: URL: https://github.com/apache/maven-verifier-plugin/pull/67
Carries out the CleanUP step of the [retirement plan](https://maven.apache.org/developers/retirement-plan-plugins.html) for this plugin, following the vote that passed on 2025-11-29 with nine +1s — [[RESULT] [VOTE] Retire Maven Stage & Maven Verifier Plugins](https://lists.apache.org/thread/j0dqo61wlm7fxsrvgq0r718nzpjc1byk). | | | |---|---| | `Jenkinsfile` | deleted — drops the job from the `maven-box` folder on ci-maven.apache.org | | `.github/` (10 files) | deleted — otherwise the `stale`, `release-drafter` and dependabot workflows keep firing on a repo nobody can act on | | `.asf.yaml` | description gains ` (RETIRED)` | **This must merge before the INFRA archive request.** An archived repo is read-only, so anything left behind is frozen permanently and costs an unarchive/fix/re-archive round-trip to correct. No final release is involved: the vote resolved explicitly not to make one, so 1.1 remains the last published version. Twin of apache/maven-stage-plugin#75, which does the same for the other plugin in that vote. Two things deliberately left for a decision rather than done here: - **The 5 open issues.** All are enhancement/bug reports migrated from JIRA in January 2026. The retirement plan says to close report-type issues before archiving, since they cannot be triaged afterwards — but that is 5 replies to other people's reports, so it should be a conscious call rather than a side effect of this PR. - **The `mvn4` branch.** Unlike stage-plugin's, it is not just an aggregator commit: it carries 3 commits, including "Switch to the new api" from 2022-02-24. Deleting it or letting the archive freeze it are both defensible; its tip is `7cf8b034a2b8526d34719c8df22ed5458a1c1d3b`. Note that if it survives, its own `Jenkinsfile` survives with it. Expect no CI on this PR — it deletes the workflow that would run it. <sub>Drafted with Claude — please verify</sub> -- 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]
