> > Anything else would suggest this is a release, and it's not.
Can you explain a bit more this please? What do you mean "it's not"? The build is currently green and stable. Users feedback is good. We do follow Apache rules in terms of quality, licensing and any other legal. We don't have any snapshot dependency as far as I know. I have the feeling this statement is related to the TCK note I added, that's why I am asking. -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Apr 25, 2016 at 12:24 PM, Andy Gumbrecht <[email protected]> wrote: > I get the 7.1 idea, but think we should just continue down the milestone > path until we have a release. 7.0.0-Mx. Anything else would suggest this is > a release, and it's not. > > http://www.tomitribe.com - @AndyGeeDe - On a small screen device. > On 25 Apr 2016 11:20, "Jean-Louis Monteiro" <[email protected]> > wrote: > > > My 2 cts > > > > We have 3 milestones of the TomEE 7.0.0. People already using it are > > expecting a final version, and I agree with that. > > > > Tomcat 8.5 already integrated to master brings an important feature > HTTP/2 > > we want to have and offer to our users. Tomcat 8.5 is fully backward > > compatible with Tomcat 8.x ( x < 5). > > > > So I don't see any issue in having TomEE 7.0.0 final released on the > master > > and already integrating Tomcat 8.5. > > > > I understand Romain's point to reflect Tomcat jump in terms of version, > but > > having a TomEE 7.1.0 would appear weird if we don't have a TomEE 7.0.0. > > > > If we really want to follow Romain's point and reflect the Tomcat > > versioning jump, I'd go with first a 7.0.0 based on the M3 with a couple > of > > bugfixes but with Tomcat 8.x (x < 5) and also a TomEE 7.1.0 with Tomcat > 8.x > > (x >= 5). > > > > So my view is > > > > Option 1/ > > TomEE 7.0.0 with Tomcat 8.x (x >= 5) with HTTP/2 > > > > *or* > > > > Option 2/ > > TomEE 7.0.0 with Tomcat 8.x (x < 5) without HTTP/2 > > + > > TomEE 7.1.0 with Tomcat 8.x (x >= 5) with HTTP/2 > > > > > > *Side note*: we don't have any Java EE 7 TCK yet and I don't expect it to > > happen anytime soon. > > So even if not certified, I'd still go with a final release (non > certified) > > of TomEE > > > > Jean-Louis > > > > > > -- > > Jean-Louis Monteiro > > http://twitter.com/jlouismonteiro > > http://www.tomitribe.com > > > > On Mon, Apr 25, 2016 at 11:02 AM, Martin Funk <[email protected]> > > wrote: > > > > > To my impression there are customers out there with an eye on TomEE to > > get > > > the JEE 7 certification. > > > And with the current version scheme they expect the TomEE 7.0 to be > JEE 7 > > > conform, so in > > > my believe they'd be surprised to see an TomEE 7.1 version before 7.0 > is > > > JEE 7. > > > They'd expect it to be JEE 7 conforming before bumping up the minor > > version > > > number. > > > > > > Technically I think I understand the issue and I could explain, if I > can > > > get into discussion with the customer. > > > The problem are the customers that you can't discuss with, that are > > scared > > > of before you get a chance to talk to them. > > > > > > mf > > > > > > 2016-04-25 10:12 GMT+02:00 Romain Manni-Bucau <[email protected]>: > > > > > > > Le 25 avr. 2016 09:39, "Martin Funk" <[email protected]> a écrit > : > > > > > > > > > > A user's opinion here. > > > > > Getting TomEE to be JEE 7 compliant is a big obstical whereever I > go. > > > > > So releasing a 7.1 before 7.0 is JEE 7 compliant would lead to a > big > > > need > > > > > of explenaiton. > > > > > > > > > > > > > What does miss in this thread as explanation? Trying to get how > people > > > > percieve versions. They asked for our versioning page and now they > ask > > us > > > > to not respect it I understand - so hopefully I miss something ;) > > > > > > > > > People I talk to will not touch TomEE before it is JEE 7 compliant. > > > > > > > > > > > > > That's not a blocker or do I miss anything? > > > > > > > > > mf > > > > > > > > > > 2016-04-25 4:00 GMT+02:00 John D. Ament <[email protected]>: > > > > > > > > > > > On Sun, Apr 24, 2016 at 6:59 PM Romain Manni-Bucau < > > > > [email protected]> > > > > > > wrote: > > > > > > > > > > > > > Le 25 avr. 2016 00:36, "John D. Ament" <[email protected]> > a > > > > écrit : > > > > > > > > > > > > > > > > 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. > > > > > > > > > > > > > > Do you think releasing a version which changes structurally > with > > > the > > > > same > > > > > > > minor is less confusing - was my fear ? > > > > > > > > > > > > > > > > > > > Maybe your fears aren't clear. Granted I haven't tried tomcat > 8.5. > > > > Are > > > > > > you saying that using Tomcat 8.5 causes TomEE to have a different > > > > directory > > > > > > structure or something? Or what structurally is the issue here? > > Its > > > > not > > > > > > clear. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 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. > > > > > > > > > > > > > > > > > > > > > > As mentionned 2.x would break tools - tomee ones which is ok > but > > > > several > > > > > > > externals including maven/ivy (gradle) based ones so I'm > against > > it > > > > and > > > > > > > prefer to confuse vs break. > > > > > > > > > > > > > > > > > > > How does it break maven/ivy/gradle? > > > > > > > > > > > > > > > > > > > > > > > > > > About doing a 7.0 with master: if everyone wants I m happy to > > > > promote M3 > > > > > > > as final - we can disucss later if we backport or not things. > > > > > > > > > > > > > > > > > > > > I think the part I don't understand is what benefit is there to > > > release > > > > > > TomEE ?? based on Tomcat 8.0 when 8.5 is coming out now. Maybe > the > > > > bigger > > > > > > question is does it make sense to release TomEE 7 based on Tomcat > > > 8.5? > > > > > > > > > > > > > > > > > > > If everyone wants just to move on 7.0 I'm also happy with it > but > > > > please > > > > > > ack > > > > > > > we delete all the minor part with NO replacement of the page > > > > > > > http://tomee.apache.org/tomee-version-policies.html - we never > > > > respects > > > > > > > any > > > > > > > mathematical logic for minors and cause of our stack I guess > > we'll > > > > never > > > > > > > do. > > > > > > > > > > > > > > Excepted Alex everyone feedback was 7.0. > > > > > > > > > > > > > > @Alex: wyt about it? > > > > > > > > > > > > > > Anyone feeling something else before we use that? > > > > > > > > > > > > > > > John > > > > > > > > > > > > > > > > On Sun, Apr 24, 2016 at 6:05 PM David Blevins < > > > > [email protected] > > > > > > > > > > > > > > > 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 < > > > > > > > [email protected] > > > > > > > > > > > > > > > > > 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" < > > > > [email protected]> > > > > 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 < > > > > > > > [email protected] > > > > > > > > > > > > > > > > > > > >> 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" < > > > > [email protected]> > > > > > > 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 < > > > > > > > > > [email protected] > > > > > > > > > >>> > > > > > > > > > >>>> 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? > > > > > > > > > >>>> > > > > > > > > > >>>> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
