slachiewicz commented on issue #11858: URL: https://github.com/apache/maven/issues/11858#issuecomment-5451749207
Hi @slawekjaranowski — status update on this cleanup, based on a full re-verification of the repo today (2026-08-28): ## Current state - Branch count is down from ~131 to **125**. Several branches listed here are already gone: `markdown`, `close`, `resolver-locking-mode`, `feature/gh-11074-recursive-project-url-it`, `logger-levels-config` (PR #600 closed), `MNG-7532` (PR #793 merged), `prefix` (PR #10971 merged), `feature/generate-plugin-descriptor-bean-and-reader-from-model` (PR #862 closed today). - ⚠️ The PR states in the issue table are stale (March snapshot). Current states verified: **#793 MERGED**, **#10971 MERGED**, **#600, #833, #1095, #1035, #2219 CLOSED** — so only **4** listed branches still have open PRs: `mdo` (#2023), `jenkinsfile-mimir` (#2208), `release-scripts` (#2473), `11582` (#11583). - One branch missing from the list: `pre-reset-master` (last commit **2017-12-11**) — oldest unlisted branch, clear delete candidate. - Note: the migrated GitHub issue for MNG-4347 ([#5813](https://github.com/apache/maven/issues/5813)) was closed as completed on 2026-03-23 — JIRA states should not be trusted anymore for triage. - Thanks @Hiteshsai007 — the ahead/behind analysis matches what I verified. ## Done today - 🗑️ Deleted: `branch-maven-4.0.0-rc-2`, `slf4j-log4j2.5`, `feature/plugin-descriptor-with-extensions` (PR #833 closed), `MNG-7758_workaround` (PR #1095 closed) - 🏷️ Created archive tags before any future branch removal, so old maintenance lines stay recoverable: - `archive/maven-2.2.x` → 3599313 - `archive/maven-3.0.x` → b4cdbb2 (Note: no need to remove branch protection to create tags — tags point at commits, and the protected branches stay in place.) - 🤖 Opened PR #12886: **monthly scheduled workflow** that lists branches with no commits in >6 months and no open PR (skipping protected branches), and posts/updates a report on this issue — turning this cleanup into a routine. ## Remaining / suggestions - ⚙️ **"Automatically delete head branches"** repo setting requires **admin** rights — needs someone with admin on the repo to enable it in Settings → General → Pull Requests. This would prevent most future stale branches at the source. - Other verified delete candidates (no open PR, abandoned 1–10 yrs): `pre-reset-master`, `slf4j-gossip`, `maven-3.x-next`, `MPOM-215`, `MNG-6732`, `mng-5668-poc`, `MNG-4463`, `MNG-5567`, `MNG-6829`, `MNG-6825`, `MNG-6889`, `MRESOLVER-94`, `MNG-6135`, `MNG-5227`, `MNG-5563`, `MNG-4645+MNG-6772`, `MNG-5001`, `MNG-7384`, `MNG-7422`, `maven-parent-35`, `first-module-fail`, `MNG-7276`, `MNG-7273`, `fix-site-generation`, `MNG-7641`, `MNG-7938`, `code-enhancement-jdk17`, `refactor/getVersionConstraint`, `qube`, `order`, `more`, `local`, `map`, `mvnup`, `feature/optimize-composite-bean-helper-performance` - Committer judgment still needed: `maven-3.8.x-resolver-1.7.x/1.8.x/1.9.x`, `MNG-6960-3.8.x` (3.8.x is EOL), `mvn4` - Suggest updating the issue table to strike deleted branches and refresh PR states. -- 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]
