Technically, you are right. We request to verify issues with 3.8.x and
move to if the issue is resolved. But that does not happen very often,
IMHO. I wouldn't even object to raise to 3.8.1, but this is another
discussion.
Am 2022-03-13 um 16:45 schrieb Sylwester Lachiewicz:
Everything before 3.8.x now it's obsolete, because we no longer provide or
plan any patches to the 3.5x or 3.6x line (bugfix or security)
Sylwester
niedz., 13 mar 2022, 12:48 użytkownik Michael Osipov <[email protected]>
napisał:
Folks,
as you might now we are dragging old luggage over and over with every
new year. We are making (little) progress with cleansing, skimming and
updating of our components.
I'll will make a radical proposal I have already discussed privately
with other fellow committers over Slack:
Raise the entire baseline to Maven 3.5.4, all of our raises have been
intermediaries. Reasoning:
* Maven 3.5.4 is almost 4 old, it is settled
* Everything before we shouls consider ancient, if you haven't moved
yet, you will not and it will be your problem.
* It is the first version which uses Maven Resolver [1]
* It will free resources to test with previous releases which most don't
do anyway
* Maybe this will make it even easier to migrate to the upcoming Maven
Core API
WDYT?
Michael
PS: I don't even mind 3.6.3 personally, thought I don't this benefit.
[1]
https://cwiki.apache.org/confluence/display/MAVEN/Maven+Ecosystem+Cleanup#MavenEcosystemCleanup-ResolverandMaven
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
