yes to try to make sure Maven 4.0.0 will run smoothly on Java 24

on tying Maven 4.0.0 release to Jira to GH Issues migration: is there a strong 
reason for coupling these 2 huge beasts?


longer analysis:

Jira to GH Issues migration has started everywhere (66 as of now, if tracking 
is accurate [1]), but near nothing is finished

concretely: how many releases of simple plugins or components have been done 
with GH Issues and associated release notes prepared by the new approach? and 
what if I add "by people other than Slawek"?
hint: [2]

We have so many small plugins or components to get experience. I expected that 
by mid-may we would have huge experience with the new approach: that's not the 
case

Maven core is the biggest, most complex, migration we have: I'd be seriously 
worried if we couple the Maven 4.0.0 release with Jira to GH Issues migration

Regards,

Hervé


[1] https://cwiki.apache.org/confluence/display/MAVEN/
JIRA+to+GitHub+Issues+switching

[2] https://lists.apache.org/list?dev@maven.apache.org:lte=1M:[VOTE]%20Release

Le mercredi 21 mai 2025, 22:03:06 CEST Matthias Bünger a écrit :
> Hey,
> I‘ve lost the overview to the java 24 issues, but if I got it right the sisu
> 0.94 can handle it. So if we are fine on running on java 24 and our 4.x
> plugins (there are  some in beta etc, look at the update parent to 44 of
> source-p for example) are final too, I think we are good to go. Why the
> plugins? Think it’s not good to say „here main is final, use the 4.x
> plugins of those exist, bit yes they are alpha/beta“.
> 
> Another point we can consider: finish enable github issues for all relevant
> projects to make it easier and consisten for users to provide
> feedback/issues. Slawek and I are close to finish. If I have it in mind
> correctly about 15 repos left, including maven itself (long standing draft
> afair).
> 
> Have a good night everyone.
> Matthias
> 
> Sent from mobile
> 
> > Am 21.05.2025 um 08:12 schrieb Guillaume Nodet <gno...@apache.org>:
> > 
> > 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





---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to