slachiewicz opened a new pull request, #1639:
URL: https://github.com/apache/maven-site/pull/1639
Step 3 of the retirement plan was written for the repository alone and has
drifted. Everything here came from actually retiring `maven-pdf-plugin`,
`maven-stage-plugin` and `maven-verifier-plugin` — each gap below cost either a
follow-up commit or left something wrong in public.
**New steps**
- **Ordering, stated up front.** Repository changes must merge before the
INFRA archive request. It is the one hard constraint in the procedure and the
page never said so; getting it wrong costs an unarchive/fix/re-archive round
trip.
- **Delete the Actions run history and caches.** Removing `.github` stops
new runs but leaves the old ones frozen in an archived repository — 1036 runs
on stage, 787 on verifier, six caches each.
- **Delete stale topic branches.** Also frozen, and one still carrying a
`Jenkinsfile` can keep a build job alive.
- **Replace the README**, which otherwise goes on explaining how to fork the
repository and open pull requests forever.
- **Ask INFRA for the Jira project** in the same ticket as the repositories,
as MPDF got under INFRA-26617.
**Corrections**
- The file is `Jenkinsfile`, not `.Jenkinsfile`, and CI has been
`ci-maven.apache.org` for some time — the `builds.apache.org` link is dead.
- "Remove distribution" now says explicitly to remove the `.asc` and
`.sha512` too. `maven-pdf-plugin` lost its zip in r75632 and kept both
signature files, so downloads.apache.org served a PGP signature for a file that
404s — from March 2025 until this month.
- `maven-sources` needs the aggregator `<module>` removed alongside the
manifest entry, or the aggregator build breaks for everyone who syncs it.
**The `.asf.yaml` step** gains the three settings that turned out to behave
unintuitively. Each was verified by reading `infrastructure-asfyaml` rather
than inferred, since its README documents none of it:
| Setting | Behaviour |
|---|---|
| `homepage` | `metadata.py` applies any truthy value but skips an absent or
empty one, so it can be **set** but never **cleared**. Pointing it at
maven.apache.org is therefore better than deleting the key. |
| `autolink_jira` | `autolink.py` only calls `create_autolink`; there is no
deletion path, so removing the key leaves existing autolinks behind. |
| `features.issues` | `features.py` passes
`has_issues=features.get("issues", False)`, so dropping the key while keeping
the `features` block **disables issues** and hides every report the repository
holds. Worth leaving enabled — an archived repo keeps its issues readable. |
`mvn spotless:check` passes.
<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]
