Same fear for me. We'll not get any Java EE 7 TCK at Apache. So waiting only penalize the project.
-- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Apr 25, 2016 at 2:39 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Hi Jon, > > nothing more than the proposal "To make it clear this is a VOTE by LAZY > consensus to use 7.0.0 as next tomee release version." = starting a [VOTE] > Apache TomEE 7.0.0 following this vote. > > "What is GA" - guess you mean more Final since GA just means available and > milestone are king of GA by definition? I think it is what the *project* > judges stable enough. I think it is very important for us to break this > insane dependency to Oracle we don't control and having delayed us of at > least 2 years. This means you can see the vote as "is master stable enough > to be released as Final and no more as milestone which supposes implicitly > no quality guarantee?". > > Legally we can do Final (0.0) when we want certified or not (TomEE is an > autonomous ASF project). > > If we get TCK and certified we can do a 8.0.0 if you want to "mark" it but > that's another topic we'll cover if relevant at that point. > > Does it clarify the intent? > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <http://rmannibucau.wordpress.com> | Github < > https://github.com/rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > <http://www.tomitribe.com> | JavaEE Factory > <https://javaeefactory-rmannibucau.rhcloud.com> > > 2016-04-25 14:28 GMT+02:00 Jonathan Gallimore <jgallim...@tomitribe.com>: > > > I'm not sure what I'm voting for and how this relates to the other thread > > "Next release 7.1". > > > > Is it both of the following? > > > > * No change in version numbering (i.e. continue with 7.0.0.M1, M2, M3, M4 > > etc until we get to a 7.0.0 GA) > > * Include Tomcat 8.5 and later in the 7.0.x series with no separate fork > > for Tomcat 8.5 support > > > > If it is, I'd expect the next release to be a 7.0.0.M4, with Tomcat 8.5 > > included. > > > > The next question is - what is GA? As we aligned with Java EE version > > numbering, I'd expect a 7.0.0.GA to be a JEE 7 certified released, at > > least > > for webprofile, and I think it needs to be very clearly communicated if > > that is not the case. Are their any legal implications of releasing a > TomEE > > 7.0.0 GA that is not certified? > > > > Jon > > > > On Mon, Apr 25, 2016 at 1:01 PM, Romain Manni-Bucau < > rmannibu...@gmail.com > > > > > wrote: > > > > > Hi guys, > > > > > > seems we'll reach a consensus soon on the fact we have to use 7.0 for > > next > > > release so trying to make the global topic moving forward ie the next > > tomee > > > release version. > > > > > > Using milestones doesn't reflect code state and has the following > > > disadvantages: > > > > > > - we have no clue yet we'll sort soon oracle discussions > > > - it prevents tooling and cloud integration (this thread is not about > > > discussing it is for good reasons or bad) > > > - milestones seems to impact some user/manager minds where it can be > more > > > stable than some previous final releases, then also impacts us as a > > > community since we don't reach the usage we should > > > - we are stable since months, if we stop we can still change the > version > > > later if desired but today we are > > > > > > To make it clear this is a VOTE by LAZY consensus to use 7.0.0 as next > > > tomee release version. > > > > > > [+1] yes let's do it > > > [ 0] what are you speaking about? meh don't care > > > [-1] no cause ${reason} is a blocker > > > > > > Vote is open for 72 hours. > > > > > > Romain Manni-Bucau > > > @rmannibucau <https://twitter.com/rmannibucau> | Github > > > <https://github.com/rmannibucau> | LinkedIn > > > <https://www.linkedin.com/in/rmannibucau> | JavaEE Factory > > > <https://javaeefactory-rmannibucau.rhcloud.com> > > > > > > > > > > > -- > > Jonathan Gallimore > > http://twitter.com/jongallimore > > http://www.tomitribe.com > > >
