-1 for release, +1 for rc4. Reason: What Sylwester said, plus Nikita from JetBrains asking nicely. They (JB) would love to see API stability so they can ship an IntelliJ IDEA release in time with Maven 4. This of course applies to all other IDEs.
Nikita is on #maven in slack, maybe also subscribed here? idk. Anyway, really strong reasons to do an RC4 first. This should not be hasted. - Ben Am Fr., 23. Mai 2025 um 00:05 Uhr schrieb Sylwester Lachiewicz <slachiew...@gmail.com>: > > I would go for rc4 because we still have API changes after rc3 and our > plugins needs adjustments that could again require another, smaller > changes. > With current state of plugins 4.x they can't be used with latest (master) > version so we could offer only 3.x for Maven 4. > Not so big issue for many users but without semi automatic way to move > plugin to new public API we are selling new "untested internally". > > In my opinion, if we could have releases of core plugins based on rc4 API > and our CI/CD pipelines runs also under Maven 4 - it would be safer. > > Sylwester > > śr., 21 maj 2025, 08:12 użytkownik Guillaume Nodet <gno...@apache.org> > napisał: > > > Hey Maven Devs, > > > > We're gearing up to release a new version from the master branch. I'm > > thinking we should go for 4.0.0 instead of rc-4. What do you all think? Any > > feedback or ideas on the versioning or release plan? Let’s hear it! > > > > Cheers, > > > > Guillaume > > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
