Hi,
for me this is a valid idea and way. 1.x is clearly stated to be for
Maven 3 and raising the minor version due support for a new minor
version of Maven 3 suites the sem ver convention as well takes into
account the larger changes between Maven 3.9 and Maven 3.10 (resolver etc).
What remains I can't really say. We have three dependabot-PRs for 1.x
branch, where I guess lifting slf4j to 2.0 only applies for the
to-be-created 1.1 / Maven 3.10 change - as we decided for other plugins.
There are also some improvements/fixes by Sywester and Guillaume, which
I think could be applied. The support for ARM64 (Draft) sounds also
reasonable for a minor upgrade.
Matthias
Am 09.10.2026 um 23:56 schrieb Tamás Cservenák:
Howdy,
Now with 3.10.0 out of the door, we may want to plan for new mvnd 1.x
release.
Long time ago Guillaume and I agreed (informally) to create mvnd-1.1.x
branch and make mvnd integrating Maven 3.10.x carry 1.1.x version. This
would leave 1.0.x free for subsequent patch releases for existing 1.0.x
line (but I doubt there will be any), and 2.0.x continues to follow Maven
4.0.x as before.
So the questions are:
1. Are we fine with this? If yes, when to create mvnd-1.1.x branch?
2. What remains for mvnd 1.1.0 release?
Thanks
T
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
