Delete stale branches

[desruisseaux]

The https://github.com/apache/maven-surefire/branches/stale page lists 25 stale branches, half of them being at least 3 years old. I suspect that the mvn4 branch, for example, is not applicable anymore since Maven 4 got many changes in the last years. Does someone familiar with those branches could delete the obsolete ones?

[Bukama]

Please do for all maven repositories 🙈

[desruisseaux]

Please do for all maven repositories

Created a more detailed issue for the compiler plugin: apache/maven-compiler-plugin#977

[Tibor17]

@ *desruisseaux* Pls keep them. I want to review my branches. There are important things which still make sense. Tibor

…

On Sun, Oct 5, 2025 at 12:31 PM Martin Desruisseaux < ***@***.***> wrote: *desruisseaux* created an issue (apache/maven-surefire#3195) <#3195> New feature, improvement proposal The https://github.com/apache/maven-surefire/branches/stale page lists 25 stale branches, half of them being at least 3 years old. I suspect that the mvn4 branch, for example, is not applicable anymore since Maven 4 got many changes in the last years. Does someone familiar with those branches could delete the obsolete ones? — Reply to this email directly, view it on GitHub <#3195>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH7ERYOUE6BZLGKSN7GXNL3WDXQFAVCNFSM6AAAAACIKLSI3KVHI2DSMVQWIX3LMV43ASLTON2WKOZTGQ4DINRWG43TQMI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[desruisseaux]

No problem, I do not intend to delete anything myself (it is a request for peoples who know these branches). But do we need to keep all of them? For example, I really doubt that mvn4 is still applicable. Could we list the branches to keep?

[Tibor17]

I'll let you know. T

…

On Mon, Oct 6, 2025 at 2:53 PM Martin Desruisseaux ***@***.***> wrote: *desruisseaux* left a comment (apache/maven-surefire#3195) <#3195 (comment)> No problem, I do not intend to delete anything myself (it is a request for peoples who know these branches). But do we need to keep all of them? For example, I really doubt that mvn4 is still applicable. Could we list the branches to keep? — Reply to this email directly, view it on GitHub <#3195 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAH7ER3255JBGHQXROKUFAL3WJQ6JAVCNFSM6AAAAACIKLSI3KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGNZRGQ4TANZTGM> . You are receiving this because you commented.Message ID: ***@***.***>

[Tibor17]

@desruisseaux
I will review the branches this weekend.
@Bukama
Right to say: "Motivate ASF members to review something" over <do = remove> "do for all maven repositories". The nonfinancial motivation was perhaps missing, and the right is a human attention (how? maybe a problem!). This makes the open source.

[Tibor17]

@desruisseaux
We can remove one branch release/2.22.3. Well, I was working hard on 2.22.3, unfortunately I did not release it.

Those other branches named with big letters are mine, and I would like to take over control of them, meaning I want to work on them.

Thx