Le dim. 29 juil. 2018 à 17:39, Gurkan Erdogdu <cgerdo...@gmail.com> a écrit :
> > > > If you accept SNAPSHOTs in that statement then it is since months. > > > > For me, this statement is only valid after you release the 8.0.0-SNAPSHOT. > Some couple of user can internally deploy the SNAPSHOT version in your > projects, but you can not assume that every user was doing this because the > 8.0 branch has not been formally released :) > Agree, but the same users who don't deploy snapshots in prod will not deploy milestones or alpha/beta in prod so you don't get the feedback you expect doing that. Also if you have any incertitude about the integration feel free to fix it or ask for help on it but compared to a 7.x we have a very huge test stack validating a lot of cases so we are as safe than from the 1.x to the 7.x. To give you an idea all the version between the 1.0 and 1.5 have been a pain but since 1.5 we sometimes had some issues or spec lack but no huge regressions. 8.x is exactly at the same level and the stack we use already had all the small releases ensuring we are confident in them (compared to releasing with 10 libraries in x.0.0). > Regards. > Gurkan > > On Sun, Jul 29, 2018 at 6:32 PM, Romain Manni-Bucau <rmannibu...@gmail.com > > > wrote: > > > Le dim. 29 juil. 2018 à 17:30, Gurkan Erdogdu <cgerdo...@gmail.com> a > > écrit : > > > > > At a minimum, if some users (move from 7.0.x to 8.0.x) are successfully > > > used it in production systems for a period of time, then I can call it > > > stable release. > > > > > > If you accept SNAPSHOTs in that statement then it is since months. > > > > > > > At the first release, when you say that it is production > > > ready, it is somebit unrealistic. But, if you still want to release it > as > > > 8.0.0, you can warn the user that this is the first release and not > ready > > > for production. > > > Anyway, I just wanted to share my opinion. If the project members want > to > > > go this way, you can absolutely do. > > > Regards. > > > Gurkan > > > > > > On Sun, Jul 29, 2018 at 6:16 PM, Romain Manni-Bucau < > > rmannibu...@gmail.com > > > > > > > wrote: > > > > > > > This is actually what we did since the beginning of TomEE. > > > > Also keep in mind milestone, alpha, beta = don't even look at the > > release > > > > for all users who don't want to check a SNAPSHOT so at the end the > gain > > > of > > > > doing a milestone is mainly to loose time in a release process and > not > > to > > > > get any feedback - at least that's what we saw here. Therefore the > fact > > > to > > > > directly go live is probably saner and doesn't prevent to fix issues > > > > quickly. > > > > > > > > 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:14, Gurkan Erdogdu <cgerdo...@gmail.com> > a > > > > écrit : > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
