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]
