At the end of the day, nobody has felt strongly enough about https://git1-us-west.apache.org/repos/asf?p=maven.git;a=commit;h=07b8477b to veto or even -0.5 that commit.
I know we have been having the discussion here, but to me it seems like these are "bolting the stable doors after the horse has bolted" <demagogue> That commit has stood for more 6 days, and as I understand it, in C-T-R the veto has to land within 3 days or lazy consensus implies everyone approves. So the vote was called (by virtue of the commit), the results are in (by lazy consensus) and everyone agreed 3.3.0 is Java 7 ;-) </demagogue> I guess the point I am making: Does anyone feel strongly enough about 3.3.0 being Java 7 to commit a revert of 07b8477b? On 11 March 2015 at 07:35, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > Le mardi 10 mars 2015 01:22:29 Jason van Zyl a écrit : > > I agree we're spending too much energy > we have a constructive discussion to make a community decision: yes, it > costs > energy (not so much since the discussion is constructive), but it's useful > > > but I don't plan to roll anything > > back. I do not want to support the rather large feature set change across > > 1.6 and 1.7 because it will be a huge maintenance burden. It's entirely > > unrealistic to try and support 1.6 and 1.7 given the activity in the core > > by so few. If we cut this release and then we switch to 1.7 the 3.3.0 > will > > pretty much become instantly dead because I know we'll flip over to 1.7 > > features quickly and i doubt anyone is going to backport anything and > there > > are likely going to be issues with all the new features and then a user > is > > going to be forced to update anyway to get the fixes. If you want all the > > new features then too bad, upgrade to 3.3.0 and use 1.7. I really do not > > want to continue developing with 1.6 because I think it's a waste of time > > and energy. > I perfectly understand this reasoning: and I know I didn't do the backport > to > 3.0.6 that I prepared because I had the exact same feeling "if you want all > the new features then too bad, upgrade", and that our users understand it > > personnally, I can live with both choices: we have the pros and cons of > each > and will be able to explain our choice in the release notes > > Regards, > > Hervé > > > > On Mar 10, 2015, at 12:56 AM, Kristian Rosenvold > <kristian.rosenv...@gmail.com> wrote: > > > I think we're spending far too much energy on this discussion. Roll > back > > > to > > > 1.6/1.6 and make the 3.4 1.7. > > > > > > > > > Kristian > > > > > > 2015-03-10 8:50 GMT+01:00 Hervé BOUTEMY <herve.bout...@free.fr>: > > >> Java 7, ie 3.2(Java 6)/3.3(Java 7+current changes) > > >> or > > >> Java 6, ie 3.2(Java 6)/3.3(Java 6+current changes)/3.4(Java 7, ~1 > month > > >> later) > > >> ? > > >> > > >> Regards, > > >> > > >> Hervé > > >> > > >> Le lundi 9 mars 2015 09:35:30 Jason van Zyl a écrit : > > >>> Yes, I'll leave it until Wednesday to see if anyone has any issues > > >> > > >> running > > >> > > >>> master and then I'll stage the release. > > >>> > > >>> On Mar 8, 2015, at 6:42 PM, Hervé BOUTEMY <herve.bout...@free.fr> > wrote: > > >>>> notice that this would be a de-facto Maven versionning pattern: > > >>>> 2.0 (Java 1.4)/2.1(Java 1.4+changes)/2.2(Java 5) > > >>>> 3.0 (Java 5)/3.1(Java 5+changes)/3.2(Java 6) > > >>>> > > >>>> then 3.2(Java 6)/3.3(Java 6+changes)/3.4(Java 7), if we announce the > > >>>> pattern and do the 3.4 release something like one month later (after > > >>>> checking that we don't need critical fix on 3.3), could match > > >> > > >> everybody's > > >> > > >>>> concern > > >>>> > > >>>> with such a plan decision, I could go for it > > >>>> > > >>>> Regards, > > >>>> > > >>>> Hervé > > >>>> > > >>>> Le dimanche 8 mars 2015 21:43:11 Robert Scholte a écrit : > > >>>>> issues for 3.2.6 have already been pushed forward to 3.3.0 *before* > > >> > > >> the > > >> > > >>>>> Java7 decision. And that's fine by me. > > >>>>> As Dennis already suggested: after 3.3.0 push JDK requirement to > 1.7 > > >> > > >> and > > >> > > >>>>> call this Maven 3.4.0 > > >>>>> A JDK requirement has too much impact for a 3.3.1, but IMHO it's > not > > >>>>> worth > > >>>>> a 4.0.0 > > >>>>> Also see previous releases when we moved forward to Java5 (M2.2) > and > > >>>>> Java6 > > >>>>> (M3.2) > > >>>>> > > >>>>> Op Sun, 08 Mar 2015 21:33:38 +0100 schreef Tibor Digana > > >>>>> > > >>>>> <tibordig...@apache.org>: > > >>>>>> @Robert > > >>>>>> source=target=1.7 after M3.3.0? You mean 3.3.1? > > >>>>>> A bit strange to make it in an incremental version since a user > would > > >>>>>> not > > >>>>>> imaging a fix version to break the system requirements in his CI > > >>>>>> regarding > > >>>>>> JDK installation. > > >>>>>> > > >>>>>> Currently the release notes for 3.2.6 is empty. > > >>>>>> So if there's really nothing to fix in 3.2.6, I would suggest to > > >> > > >> jump to > > >> > > >>>>>> 3.3.0 with JDK 7. > > >>>>>> http://jira.codehaus.org/browse/MNG/fixforversion/20821 > > >>>>>> > > >>>>>> > > >>>>>> > > >>>>>> -- > > >> > > >>>>>> View this message in context: > > >> > http://maven.40175.n5.nabble.com/move-maven-core-to-java-7-tp5827988p582 > > >> > > >>>>>> 85 > > >>>>>> 22.html Sent from the Maven Developers mailing list archive at > > >>>>>> Nabble.com. > > >>>>>> > > >>>>>> > --------------------------------------------------------------------- > > >>>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >>>>>> For additional commands, e-mail: dev-h...@maven.apache.org > > >>>>> > > >>>>> > --------------------------------------------------------------------- > > >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >>>>> For additional commands, e-mail: dev-h...@maven.apache.org > > >>>> > > >>>> > --------------------------------------------------------------------- > > >>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >>>> For additional commands, e-mail: dev-h...@maven.apache.org > > >>> > > >>> Thanks, > > >>> > > >>> Jason > > >>> > > >>> ---------------------------------------------------------- > > >>> Jason van Zyl > > >>> Founder, Takari and Apache Maven > > >>> http://twitter.com/jvanzyl > > >>> http://twitter.com/takari_io > > >>> --------------------------------------------------------- > > >>> > > >>> A man enjoys his work when he understands the whole and when he > > >>> is responsible for the quality of the whole > > >>> > > >>> -- Christopher Alexander, A Pattern Language > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> > > >>> --------------------------------------------------------------------- > > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >>> For additional commands, e-mail: dev-h...@maven.apache.org > > >> > > >> --------------------------------------------------------------------- > > >> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > >> For additional commands, e-mail: dev-h...@maven.apache.org > > > > Thanks, > > > > Jason > > > > ---------------------------------------------------------- > > Jason van Zyl > > Founder, Takari and Apache Maven > > http://twitter.com/jvanzyl > > http://twitter.com/takari_io > > --------------------------------------------------------- > > > > A master in the art of living draws no sharp distinction between his work > > and his play; his labor and his leisure; his mind and his body; his > > education and his recreation. He hardly knows which is which. He simply > > pursues his vision of excellence through whatever he is doing, and leaves > > others to determine whether he is working or playing. To himself, he > always > > appears to be doing both. > > > > -- François-René de Chateaubriand > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > > For additional commands, e-mail: dev-h...@maven.apache.org > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
