I have one question, which is recurring for every issue: what is the impact?
I understand the logic: it should fix a bug (that is told introduced in Maven 3.3.1), and the bug is explained by the logic behind the javadoc. But no pointer to any code using this method, and that shows that Maven 3.3.1 does not work any more, when previous version were ok. Then what is explained here as a bugfix could cause issues for others. I'm -1 unless I have some details on the impact Regards, Hervé Le samedi 4 mars 2017, 13:33:55 CET Christian Schulte a écrit : > Am 03/02/17 um 22:55 schrieb Stephen Connolly: > > I'd like to declare feature freeze for alpha-2 on March 9th. > > > > If a feature does not land in alpha-2 it will not be in beta-1 (i.e. Only > > bug fixes or rip out features that are causing S1/S2 issues will be in > > the diff from alpha-2 to beta-1) > > > > I am aiming beta-2 approx 2 weeks after alpha-2 and the GA approx 2 weeks > > after that. > Should we include > > <https://issues.apache.org/jira/browse/MNG-6173> > > FIX-3.5.0? It has just been reported. It also has an IT pull request. If > no one objects, I'll create a branch and later merge it to master. > > Regards, --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
