On Mon, Apr 25, 2016 at 10:20 AM, 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. > +1 My personal opinion is that in seeing a jump to a 7.1.M1, people will look for a 7.0 GA, and be confused because its missing. I know I would be. > > 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). > +1 > > So I don't see any issue in having TomEE 7.0.0 final released on the master > and already integrating Tomcat 8.5. > + 1 > > 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 > I don't have any objection to that. > > *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 > > I think this is confusing - we already have the concept of "flavours" (webprofile, jaxrs, plus, plume) which determine what features are "in the box". Mixing in whether or not you get HTTP/2 in with the version number seems confusing to me. If Tomcat 8.5 is fully backwards compatible with previous Tomcat 8.x releases (and I note that JL says it is above), I see no reason for TomEE 7.0.0.M4 onwards to use that, and include HTTP/2 support. Jon -- Jonathan Gallimore http://twitter.com/jongallimore http://www.tomitribe.com
