>From my perspective, this is not realistic. You are releasing the first version for JDK 8, MP 1 after getting 8.0 branch to master, and at the first release you are saying that this is production ready. At least, we will need to let users some time to try it and give feedbakcs. I don't say that M1 goes to M2, M3 etc. But, at least, you need to receive some feedback from the users who will move from Tomcat 7.0.x to 8.0.x. I can not tell our users that you can directly move from 7.0.x to 8.0.x at the initial release. Regards. Gurkan
On Sun, Jul 29, 2018 at 6:07 PM, Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > Being said all the stack is already in prod and the glue code is too (it is > in 7.x for most of it and some users even deploy the snapshot in prod) I > really think we should go directly to 8.0.0. Since we already decoralated > from the spec and certification for the 7.x then we don't need to use the > milestone workaround we used for the 1.x to ensure 1.0.0 was certificed. So > yes, 8.0.0 directly is really ok :). > > Romain Manni-Bucau > @rmannibucau <https://twitter.com/rmannibucau> | Blog > <https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > rmannibucau> | > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java- > ee-8-high-performance> > > > Le dim. 29 juil. 2018 à 17:04, Gurkan Erdogdu <cgerdo...@gmail.com> a > écrit : > > > If you release as 8.0.0, you means that it is production ready? Is 8.0.0 > > production ready at the first release? At least, at the first release you > > can add some indication that it is not production ready or it is the > first > > release etc such as M1, CR1. This is the general consensus on release > > process. > > Regards. > > Gurkan > > > > On Sun, Jul 29, 2018 at 4:41 PM, Romain Manni-Bucau < > rmannibu...@gmail.com > > > > > wrote: > > > > > +1, even a 8.0.0, no need of milestones > > > > > > Le dim. 29 juil. 2018 14:27, Gurkan Erdogdu <cgerdo...@gmail.com> a > > écrit > > > : > > > > > > > Hi team > > > > Sorry about this question (even discussed before lots of time) but > what > > > is > > > > the meaning of creating 7.1 branch? Just MP with JDK 8? > > > > If that's the only reason why not publish TomEE 8 with a milestone > like > > > > TomEE 8.0_M1 or something similar including MP? > > > > Possible to release TomEE 8.0.M1 using Geronimo MP implementation > > instead > > > > of using TomEE 7.1 branch? > > > > Thanks > > > > Gurkan > > > > > > > > > > > > On Thu, Jul 26, 2018 at 3:52 PM, Jean-Louis Monteiro < > > > > jlmonte...@tomitribe.com> wrote: > > > > > > > > > Everything should be merged and mistake fixed (wrong branch > deleted) > > > > > > > > > > -- > > > > > Jean-Louis Monteiro > > > > > http://twitter.com/jlouismonteiro > > > > > http://www.tomitribe.com > > > > > > > > > > On Thu, Jul 26, 2018 at 1:43 PM, Romain Manni-Bucau < > > > > rmannibu...@gmail.com > > > > > > > > > > > wrote: > > > > > > > > > > > Ok, > > > > > > then AFAIK it will not be a "work" branch but just an aggregator > > > branch > > > > > so > > > > > > I see two good compromises: > > > > > > > > > > > > 1. use tomee 7.0 (we just add a mp module with tomee-maven-plugin > > > Vn-1 > > > > to > > > > > > import MP impls and bundle it), no compile issue, tomee 7.0 stays > > > java > > > > 7 > > > > > > and MP is aligned on java 8 > > > > > > 2. we make 7.1 directly a branch and we release it at the same > time > > > > than > > > > > > 8.0.0 > > > > > > > > > > > > wdyt? > > > > > > > > > > > > Romain Manni-Bucau > > > > > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > > > > > <https://rmannibucau.metawerx.net/> | Old Blog > > > > > > <http://rmannibucau.wordpress.com> | Github <https://github.com/ > > > > > > rmannibucau> | > > > > > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book > > > > > > <https://www.packtpub.com/application-development/java- > > > > > > ee-8-high-performance> > > > > > > > > > > > > > > > > > > Le jeu. 26 juil. 2018 à 12:52, Jonathan Gallimore < > > > > > > jonathan.gallim...@gmail.com> a écrit : > > > > > > > > > > > > > No. As far as I'm concerned its supported for as long as > someone > > is > > > > > > willing > > > > > > > to support it. I'm willing to support it, and I'm willing to > > > support > > > > > > 1.7.x > > > > > > > also. > > > > > > > > > > > > > > Jon > > > > > > > > > > > > > > On Thu, Jul 26, 2018 at 11:39 AM, Romain Manni-Bucau < > > > > > > > rmannibu...@gmail.com> > > > > > > > wrote: > > > > > > > > > > > > > > > Ok so means we drop tomee 7.0 support with next release? > > > > > > > > > > > > > > > > > > > > > > > > Le jeu. 26 juil. 2018 12:20, Jonathan Gallimore < > > > > > > > > jonathan.gallim...@gmail.com> a écrit : > > > > > > > > > > > > > > > > > On Thu, Jul 26, 2018 at 11:18 AM, Mark Struberg > > > > > > > > <strub...@yahoo.de.invalid > > > > > > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > > > > > Yes, the following steps are now up to get done: > > > > > > > > > > > > > > > > > > > > 1.) Move the current master to a tomee-7.0.x branch > > > > > > > > > > > > > > > > > > > > > > > > > > > > Done > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.) Create a new tomee-7.1.x branch, upgrade to Java8 and > > add > > > > > > > > > MicroProfile > > > > > > > > > > > > > > > > > > > > > > > > > > > > JL doing > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2.) Move the tomee-8.x branch to master and get stuff > > rolling > > > > > here > > > > > > as > > > > > > > > > well. > > > > > > > > > > > > > > > > > > > > > > > > > > > > Done. > > > > > > > > > > > > > > > > > > There was a force-push involved to update master. Hope that > > > > doesn't > > > > > > > cause > > > > > > > > > issues, but apologies if it does. > > > > > > > > > > > > > > > > > > Jon > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
