slachiewicz opened a new issue, #1079: URL: https://github.com/apache/maven-doxia/issues/1079
The Doxia 2.0.0 stack is complete, and each reporting component still carries the branch that held its Doxia 1.x line. This issue tracks retiring those branches and is the target for the `.asf.yaml` pull requests opened against each repository. ## Convention For each branch: a lightweight tag `archive/<branch>` at the tip, then the branch is deleted. The tag keeps every commit reachable; the absent branch removes the ambiguity about which line is live. Release tags are untouched. `apache/maven-jxr` was done first as a pilot — `jxr-3.4.x` is gone, `archive/jxr-3.4.x` points at `2cd6a449`, `jxr-3.4.0` is unaffected. Most of these branches appear in their repository's `.asf.yaml` `protected_branches`, which has to be edited before the branch can be deleted. That edit is all the linked PRs do. ## Branches Nothing on these is unreachable from `master`, from the successor maintenance branch, or from a release tag: | Repository | Branch | Containment | |---|---|---| | maven-doxia | `doxia-1.x` | 11 ahead, `doxia-1.12.0` tagged; remainder is a version bump | | maven-doxia-sitetools | `doxia-sitetools-1.x` | 2 commits, May 2022 | | maven-site-plugin | `maven-site-plugin-3.12.x` | MSITE-1035 is a cherry-pick of master `e71484e0` | | maven-fluido-skin | `maven-fluido-skin-1.x` | 23 ahead, `maven-fluido-skin-1.12.0` tagged | | maven-reporting-api | `maven-reporting-api-3.x` | 4 ahead, `3.1.1` tagged | | maven-reporting-impl | `maven-reporting-impl-3.x` | 12 ahead, `3.2.0` tagged | | maven-plugin-tools | `maven-plugin-tools-3.14.x` | contained in `maven-plugin-tools-3.x` | | maven-plugin-tools | `maven-plugin-tools-3.7.x` | 4 ahead, `3.7.1` tagged | | maven-invoker-plugin | `maven-invoker-plugin-3.7.x` | contained in `master` | | maven-javadoc-plugin | `maven-javadoc-plugin-3.8.x` | contained in `master` | | maven-project-info-reports-plugin | `maven-project-info-reports-plugin-3.6.x` | contained in `master` | | maven-dependency-plugin | `maven-dependency-plugin-3.7.x` | contained in `master` | | maven-pmd-plugin | `maven-pmd-plugin-3.24.x` | contained in `master` | | maven-surefire | `surefire-3.4.x` | contained in `surefire-3.5.x` | The last four are not in `protected_branches` and need no PR. `maven-plugin-tools-3.x` and `surefire-3.5.x` are the live 3.x lines and stay. `maven-checkstyle-plugin-3.4.x` was already deleted before this work started. ## What retiring them costs These branches are also the last line in several repositories that still declares `<mavenVersion>` 3.6.3, because master has moved to 3.9.16: | Repository | master | branch | |---|---|---| | maven-project-info-reports-plugin | 3.9.16 | 3.6.3 | | maven-invoker-plugin | 3.9.16 | 3.6.3 | | maven-dependency-plugin | 3.9.16 | 3.6.3 | | maven-pmd-plugin | 3.9.16 | 3.6.3 | | maven-reporting-impl | 3.9.16 | 3.1.0 | | maven-site-plugin | 3.6.3 | 3.2.5 | | maven-javadoc-plugin | 3.6.3 | 3.6.3 | The Doxia 2.0.0 stack itself targets Maven 3.6.3, so this is not a consequence of the Doxia upgrade — the prerequisite bump happened separately. It does mean that after these deletions there is no branch left from which a fix could be shipped to users on Maven 3.6.3 through 3.9.15. Those branches have had no commit since August 2024, so in practice that has been true for two years. `maven-help-plugin-3.4.x` is deliberately excluded: it has open pull requests backporting Maven-3-only fixes, and its future is being discussed on apache/maven-help-plugin#416 and #419. *This issue was created with AI assistance.* -- 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]
