+1 to JDK 5 for Maven 3.0.6: will avoid confusion for the "supported" vs "partially supported":
AFAIK, the only fully supported version has always been the latest, and only the latest: we can once again explain it then is 3.1.1"supported with security issues"? Do you plan to release 3.1.2 with MNG-5672 fix? Who will take time to do that? look at history [1] we did EOL Maven 1.x and Maven 2.x, officially with announcement, since they were really major versions But we didn't EOL 2.0.11 through an announcement, nor 2.1.0 But look at the announce for 2.0.11, which contains an important notice ** Note: the current stable release of Maven remains as Maven 2.2.1, and all users are recommended to upgrade to that version ** IMHO, the actual expectations about officially EOL'ing any minor version that we don't have sufficient time/energy to maintain is really too much or someone will have to take time corresponding to these expectations (and that won't be me) that's the spirit of removing 3.1.1 from top download links discussion: like 2.1.x, 3.1.x was an interim version before we added JDK6 upgrade to Aether change And when releasing 3.0.6, this discussion shows that an important point will be to add in the announce following notice: ** Note: the current stable release of Maven remains Maven 3.2.3, and all users are recommended to upgrade to that version ** Perhaps we can send an announce that 3.1.1 is discontinued and users should upgrade to 3.2.3, or if stuck with JDK5 either downgrade to 3.0.5 or, better, use toolchains Perhaps that would be the toolchain promotion we're talking about, without focusing only on "EOL" message Regards, Hervé [1] http://maven.apache.org/docs/history.html Le mercredi 29 octobre 2014 19:21:03 Karl Heinz Marbaise a écrit : > Hi, > > On 10/29/14 7:33 AM, Baptiste Mathus wrote: > >> no outstanding change in 3.2.x that blocks 3.1.x users from upgrading to > > > > 3.2.x, isn't it? > > > > Didn't double checked, but IIRC 3.1.1 still uses JDK5. 3.2.x uses JDK 6. > > That may be a change you want to have in mind, though I personally don't > > care about JDK 5. > > Maven 3.0.5, 3.1.1 are JDK 5 based > > Maven 3.2.X is JDK 6 based... > > > If we make a 3.0.6 release ok but only JDK 5 based....otherwise it would > break the prerequisite line...afterwards we could define EoL ...for > 3.0.X line...(see schedule) > > To get rid of the 3.1.X line as the mood sounds here (me too)...just > declare it only to fix real bugs but not adding new features...which > should be done in 3.2.X which is the recommended line for usage... > > Just removing the download i don't like it...better to make hint's on > the pages to prefer 3.2.X....instead ... > > > so my suggestion schedule: > > Make a final release 3.0.6 JDK 5 based... > > Define Maven 3.0.X line as only partially supported with security issues. > > Define Maven 3.1.1. line as only partially supported with secority issues. > > Define Maven 3.2.X line as supported line... > > > After 3 Months we could chnage the partially supported lines into non > supported anymore... > > So we have within 3 Months which would mean 1. February 2015 get rid of > Maven 3.0.X, Maven 3.1.X and JDK 5... > > Furthermore i would suggest to make an offical announcements on the > mailing lists to make this decision public to the users.... > > > Kind regards > Karl Heinz Marbaise > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
