It doesn't make sense to jump to a 7.1 immediately without even releasing a 7.0. Just confusing from a semantic versioning standpoint.
Given the current status of the TCK & ASF, I wonder if waiting for it and claiming EE 7 compatibility at a later date would make more sense. So maybe along what Dave's mentioning and favor a TomEE 2 that's focused on EE 7 capabilities without stating that its EE7 compliant. John On Sun, Apr 24, 2016 at 6:05 PM David Blevins <david.blev...@gmail.com> wrote: > On hijacking, I think your single sentence communicated a lot more in your > head than was actually said :) I beg your patience :) > > “Why not 7.0” or “What about 7.0” are fair questions. But I see your goal > a little clearer — some way to get a TomEE version of Tomcat 8.5 out the > door. > > Let’s get some feedback. > > > -- > David Blevins > http://twitter.com/dblevins > http://www.tomitribe.com > > > On Apr 24, 2016, at 2:29 PM, Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > > > > We can do a 7.0 based on M3 and 7.1 (8.0 if you prefer) in the same vote. > > > > Basically I want master released whatever TCK status is and whatever > > version it is while > 7.0 for toolings compliance ( 2.x and 3.x are no > more > > an option IMO cause of that). > > > > Side note: speaking about 7.0 hijacks this thread which has as only > topic: > > how to get tomee http2 support out this month or next one. > > Le 24 avr. 2016 23:23, "David Blevins" <david.blev...@gmail.com> a > écrit : > > > >> I see and agree on not surprising people around a Tomcat 8.0 -> 8.5 > >> upgrade. > >> > >> I’m not seeing how discussing finishing 7.0 is highjacking. I think > >> people would find it quite confusing for us to move on to 7.1 without > >> actually doing a GA of 7.0 > >> > >> > >> -David > >> > >> > >>> On Apr 24, 2016, at 2:11 PM, Romain Manni-Bucau <rmannibu...@gmail.com > > > >> wrote: > >>> > >>> We can release a 7.0 based on M3 but not master - I dont care much for > >> this > >>> thread topic but feel free to open another thread on next 7.0.x if you > >>> care/want. Master is on tomcat 8.5 since few weeks and I d like to > >> release > >>> it once this thread passed/is done - was planning to wait until > wednesday > >>> and few more feedbacks - but to not make this important upgrade silent > >> and > >>> surprise users I d like to change the version more than a last digit. > >>> > >>> Then coming topics are: > >>> - objection for a 7.1? > >>> - what do we maintain? 1.7/7.1 - not only for the palimdrom beauty ;)? > >>> > >>> (Please dont hijack this thread commenting on these coming ones, just > >> tried > >>> to give a bit more visibility on the overall goal and why I asked about > >> 7.x > >>> versioning now) > >>> Le 24 avr. 2016 23:04, "David Blevins" <david.blev...@gmail.com> a > >> écrit : > >>> > >>>> Good thread. > >>>> > >>>> Recap of my understanding: we release 7.0 as-is and move forward to > 7.1 > >>>> based on Tomcat 8.5? > >>>> > >>>> I’d be +1 for that plan. > >>>> > >>>> > >>>> -David > >>>> > >>>>> On Apr 23, 2016, at 2:17 AM, Romain Manni-Bucau < > rmannibu...@gmail.com > >>> > >>>> wrote: > >>>>> > >>>>> Hi guys > >>>>> > >>>>> Having tomcat 8.5 now I d like to move tomee to 7.1 to show coming > >>>> release > >>>>> is not just another 7.0. > >>>>> > >>>>> Any objection? > >>>> > >>>> > >> > >> > >
