Thanks for the info. Maven updates for those not using maven wrapper take considerably longer to work around. So that was my main concern as I couldn't really see the value on this one. There are so many platforms that must be updated and outside of maven wrapper, maven is not treated as a dependency...so my concerns were the fact of not seeing issues and if 3.9.3 was so bad it needed this small set of changes. Seems all are special cases here and inherently older versions are not necessarily bad.
Sent from my Verizon, Samsung Galaxy smartphone Get Outlook for Android<https://aka.ms/AAb9ysg> ________________________________ From: Gary Gregory <garydgreg...@gmail.com> Sent: Thursday, July 20, 2023 6:19:53 AM To: Maven Developers List <dev@maven.apache.org> Subject: Re: [HEADS UP] Maven 3.9.4 plan Hi all, Is it worth including more detailed information in the release notes to short circuit questions or concerns like this one? I can't recall the last time I hear someone complaining about releasing too soon ;-) AFAIAC, if any bug fix is made available in a release, that's a good thing. I'm a fan on RERO though. Gary On Thu, Jul 20, 2023, 05:22 Tamás Cservenák <ta...@cservenak.net> wrote: > Howdy, > > mostly bug fixes in Resolver (that is shipped embedded within Maven), and > some minor fixes in Maven itself: > - resolver had 2 notable bugs, one in new BF collector (endless loop, SOEx) > that blocked VSCode Maven integration users, and a "cluster" of multiple > smaller bugs rendering provided checksum feature not quite usable. The 3rd > bug was related to a new "lock diagnostic", that was emitting false > (impossible) locks states. Rest is "general improvements" (manual route > config, timeout default value change) and POM update. There is one change > (undoes partially a change happened in 1.9.13) that is performance related, > when locking is used. > - maven had one bugfix (affecting users that may end up in endless loop in > case of plugin error, for example asciidoctor plugin users), and there was > a minor fix (bumping guava) for users who are unsavory of CVEs, mostly for > their peace of mind (as Maven itself is AFAIK not affected by this CVE, but > don't take my statement for granted). > > Of course, if you do not use any of these features like BF-collector, > provided-checksums, trying to debug locking issues or having endless loops > when some plugins fail, 3.9.4 will not make a big difference for you, but > as Romain said, we just want to "move forward", by doing regular minor > releases. > > Maven may receive more changes, as resolver is the first in the pipe, and > as all releases, takes 3 days. > > Thanks > T > > On Thu, Jul 20, 2023 at 4:18 AM Jeremy Landis <jeremylan...@hotmail.com> > wrote: > > > What exactly does this small release improve so much that it warrants a > > release this soon since 3.9.3? We scaled 3.9.3 already a while ago and > > haven't been any real issues that I can pinpoint that anything in this > > would address and make better. Clearly, I'm missing something here that > > is critical. We will upgrade right away but want to understand what this > > gets us that is so important. > > > > -----Original Message----- > > From: Tamás Cservenák <ta...@cservenak.net> > > Sent: Wednesday, July 19, 2023 11:42 AM > > To: Maven Developers List <dev@maven.apache.org> > > Subject: [HEADS UP] Maven 3.9.4 plan > > > > Howdy, > > > > Plan is as follows: > > 1. release Resolver 1.9.14 > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520MRESOLVER%2520AND%2520fixVersion%2520%253D%25201.9.14&data=05%7C01%7C%7Cfc8004efff7e4d4d28d408db890aeb53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638254452219057577%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=g%2BRlM0pMm3EdKT%2Bg%2FWAQDGKNdBS6maOWNH6PNJnJoB4%3D&reserved=0<https://issues.apache.org/jira/issues/?jql=project%20%3D%20MRESOLVER%20AND%20fixVersion%20%3D%201.9.14> > > 2. release Maven 3.9.4 > > > > > https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fissues%2F%3Fjql%3Dproject%2520%253D%2520MNG%2520AND%2520fixVersion%2520%253D%25203.9.4&data=05%7C01%7C%7Cfc8004efff7e4d4d28d408db890aeb53%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638254452219213834%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=l3PsTrRR9OSM4aXOG2ys1GbkJQaJM1DHNsHeT0LJjhU%3D&reserved=0<https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.4> > > > > I plan to start tomorrow morning (European morning). As usual, if anyone > > objects, please speak up. > > > > Thanks > > T > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > > >
