True... but we already did the same when moving from Maven 3.0.5 to 3.1.0, which is not a drop in replacement... so it would be consistent ;-)
manfred > Well, I don't see the difference, but if I put it this way: > I would be -1 to release Maven 3.1.2 requiring Java 1.6. > One shouldn't bump platform requirements in a patch version - a patch > version should be a drop-in replacement. > > On Mon, Oct 7, 2013 at 8:20 PM, Stephen Connolly > <[email protected]> wrote: >> You're voting for the wrong thing. It was already decided and announced >> that when we cut 3.2 after Sep 30th it would be 1.6 >> >> The decision is: should the next release be 3.2 or 3.1.2? To my mind >> that >> is a commit that Jason should just push and if somebody objects to the >> commit they get to maintain the 3.1.x branch ;-) >> >> On Monday, 7 October 2013, Dennis Lundberg wrote: >> >>> +1 to 1.6 for 3.2 >>> >>> On Sat, Oct 5, 2013 at 5:03 AM, Jason van Zyl >>> <[email protected]<javascript:;>> >>> wrote: >>> > Given the vote we had about releases after September does anyone mind >>> if >>> I update the source/target levels to 1.6 for the core? >>> > >>> > Thanks, >>> > >>> > Jason >>> > >>> > ---------------------------------------------------------- >>> > Jason van Zyl >>> > Founder, Apache Maven >>> > http://twitter.com/jvanzyl >>> > --------------------------------------------------------- >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> >>> >>> >>> -- >>> Dennis Lundberg >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] <javascript:;> >>> For additional commands, e-mail: [email protected] >>> <javascript:;> >>> >>> >> >> -- >> Sent from my phone > > > > -- > Dennis Lundberg > > --------------------------------------------------------------------- > 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]
