Re: [VOTE] Release Activation 2.0.0-M1

2022-05-23 Thread David Blevins
My +1 -David > On May 14, 2022, at 2:00 PM, David Blevins wrote: > > Hey All, > > We're thinking to do a release on the TomEE side and this is one of the > snapshot dependencies we have. I've prepped a 2.0.0-M1 with the idea that > being a milestone it should be fairly non-controversial

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-16 Thread fpapon
Hi, Same feedback as Romain, I don't think we need a M1. regards, François On 14/05/2022 23:00, David Blevins wrote: Hey All, We're thinking to do a release on the TomEE side and this is one of the snapshot dependencies we have. I've prepped a 2.0.0-M1 with the idea that being a

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-16 Thread Cesar Hernandez
+1 El dom, 15 may 2022 a las 6:24, Raymond Augé () escribió: > +1 (binding) > > On Sun., May 15, 2022, 5:58 a.m. Jean-Louis MONTEIRO, > wrote: > >> +1 >> >> Same feedback, I'd go for a final. There is no work remaining as far as I >> can tell >> >> Le dim. 15 mai 2022 à 09:03, Romain

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-15 Thread Raymond Augé
+1 (binding) On Sun., May 15, 2022, 5:58 a.m. Jean-Louis MONTEIRO, wrote: > +1 > > Same feedback, I'd go for a final. There is no work remaining as far as I > can tell > > Le dim. 15 mai 2022 à 09:03, Romain Manni-Bucau a > écrit : > >> Hi >> >> If we are confident to match javax/jakarta

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-15 Thread Jean-Louis MONTEIRO
+1 Same feedback, I'd go for a final. There is no work remaining as far as I can tell Le dim. 15 mai 2022 à 09:03, Romain Manni-Bucau a écrit : > Hi > > If we are confident to match javax/jakarta namespace change why not doing > a final? Errors/missing features could go in bugs. > Issue with

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-15 Thread Romain Manni-Bucau
Hi If we are confident to match javax/jakarta namespace change why not doing a final? Errors/missing features could go in bugs. Issue with milestones is the tooling support and proposed updates vs version policies so if we can avoid it I would be for it but not sure if I missed sthg. Le dim. 15

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-14 Thread Jean-Baptiste Onofré
+1 (binding) Regards JB On Sat, May 14, 2022 at 11:00 PM David Blevins wrote: > > Hey All, > > We're thinking to do a release on the TomEE side and this is one of the > snapshot dependencies we have. I've prepped a 2.0.0-M1 with the idea that > being a milestone it should be fairly

Re: [VOTE] Release Activation 2.0.0-M1

2022-05-14 Thread Daniel Dias Dos Santos
Hi +1 Thanks :) On Sat, May 14, 2022, 18:00 David Blevins wrote: > Hey All, > > We're thinking to do a release on the TomEE side and this is one of the > snapshot dependencies we have. I've prepped a 2.0.0-M1 with the idea that > being a milestone it should be fairly non-controversial to

[VOTE] Release Activation 2.0.0-M1

2022-05-14 Thread David Blevins
Hey All, We're thinking to do a release on the TomEE side and this is one of the snapshot dependencies we have. I've prepped a 2.0.0-M1 with the idea that being a milestone it should be fairly non-controversial to propose without a heads up and I haven't checked the TCK status. I know we're