Re: [VOTE] Release Activation 2.0.0-M1
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 to propose without a > heads up and I haven't checked the TCK status. I know we're not yet actively > running the signature tests on the TomEE side. > > I propose we release 2.0.0-M1 so we have some non-snapshots to work with and > come back to 2.0.0 as things look 100% on all fronts > > Staging Maven repository: > > - https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ > > The only change is conversion from javax to the jakarta namespace via > contributor Richard Zowalla. > > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] 0 Abstain (please provide specific comments) > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > -David > smime.p7s Description: S/MIME cryptographic signature
Re: [VOTE] Release Activation 2.0.0-M1
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 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 not yet actively running the signature tests on the TomEE side. I propose we release 2.0.0-M1 so we have some non-snapshots to work with and come back to 2.0.0 as things look 100% on all fronts Staging Maven repository: - https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ The only change is conversion from javax to the jakarta namespace via contributor Richard Zowalla. Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Abstain (please provide specific comments) [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. -David -- -- François
Re: [VOTE] Release Activation 2.0.0-M1
+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 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 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 mai 2022 à 07:29, Jean-Baptiste Onofré a >>> écrit : >>> +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 non-controversial to propose without a heads up and I haven't checked the TCK status. I know we're not yet actively running the signature tests on the TomEE side. > > I propose we release 2.0.0-M1 so we have some non-snapshots to work with and come back to 2.0.0 as things look 100% on all fronts > > Staging Maven repository: > > - https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ > > The only change is conversion from javax to the jakarta namespace via contributor Richard Zowalla. > > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] 0 Abstain (please provide specific comments) > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > -David > >>> >> >> -- >> Jean-Louis >> > -- Atentamente: César Hernández.
Re: [VOTE] Release Activation 2.0.0-M1
+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 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 mai 2022 à 07:29, Jean-Baptiste Onofré a >> écrit : >> >>> +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 non-controversial to propose >>> without a heads up and I haven't checked the TCK status. I know we're not >>> yet actively running the signature tests on the TomEE side. >>> > >>> > I propose we release 2.0.0-M1 so we have some non-snapshots to work >>> with and come back to 2.0.0 as things look 100% on all fronts >>> > >>> > Staging Maven repository: >>> > >>> > - >>> https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ >>> > >>> > The only change is conversion from javax to the jakarta namespace via >>> contributor Richard Zowalla. >>> > >>> > >>> > Please vote to approve this release: >>> > [ ] +1 Approve the release >>> > [ ] 0 Abstain (please provide specific comments) >>> > [ ] -1 Don't approve the release (please provide specific comments) >>> > >>> > This vote will be open for at least 72 hours. >>> > >>> > -David >>> > >>> >> > > -- > Jean-Louis >
Re: [VOTE] Release Activation 2.0.0-M1
+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 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 mai 2022 à 07:29, Jean-Baptiste Onofré a > écrit : > >> +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 non-controversial to propose without >> a heads up and I haven't checked the TCK status. I know we're not yet >> actively running the signature tests on the TomEE side. >> > >> > I propose we release 2.0.0-M1 so we have some non-snapshots to work >> with and come back to 2.0.0 as things look 100% on all fronts >> > >> > Staging Maven repository: >> > >> > - >> https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ >> > >> > The only change is conversion from javax to the jakarta namespace via >> contributor Richard Zowalla. >> > >> > >> > Please vote to approve this release: >> > [ ] +1 Approve the release >> > [ ] 0 Abstain (please provide specific comments) >> > [ ] -1 Don't approve the release (please provide specific comments) >> > >> > This vote will be open for at least 72 hours. >> > >> > -David >> > >> > -- Jean-Louis
Re: [VOTE] Release Activation 2.0.0-M1
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 mai 2022 à 07:29, Jean-Baptiste Onofré a écrit : > +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 non-controversial to propose without > a heads up and I haven't checked the TCK status. I know we're not yet > actively running the signature tests on the TomEE side. > > > > I propose we release 2.0.0-M1 so we have some non-snapshots to work with > and come back to 2.0.0 as things look 100% on all fronts > > > > Staging Maven repository: > > > > - > https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ > > > > The only change is conversion from javax to the jakarta namespace via > contributor Richard Zowalla. > > > > > > Please vote to approve this release: > > [ ] +1 Approve the release > > [ ] 0 Abstain (please provide specific comments) > > [ ] -1 Don't approve the release (please provide specific comments) > > > > This vote will be open for at least 72 hours. > > > > -David > > >
Re: [VOTE] Release Activation 2.0.0-M1
+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 non-controversial to propose without a > heads up and I haven't checked the TCK status. I know we're not yet actively > running the signature tests on the TomEE side. > > I propose we release 2.0.0-M1 so we have some non-snapshots to work with and > come back to 2.0.0 as things look 100% on all fronts > > Staging Maven repository: > > - https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ > > The only change is conversion from javax to the jakarta namespace via > contributor Richard Zowalla. > > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] 0 Abstain (please provide specific comments) > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > -David >
Re: [VOTE] Release Activation 2.0.0-M1
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 propose without > a heads up and I haven't checked the TCK status. I know we're not yet > actively running the signature tests on the TomEE side. > > I propose we release 2.0.0-M1 so we have some non-snapshots to work with > and come back to 2.0.0 as things look 100% on all fronts > > Staging Maven repository: > > - > https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ > > The only change is conversion from javax to the jakarta namespace via > contributor Richard Zowalla. > > > Please vote to approve this release: > [ ] +1 Approve the release > [ ] 0 Abstain (please provide specific comments) > [ ] -1 Don't approve the release (please provide specific comments) > > This vote will be open for at least 72 hours. > > -David > >
[VOTE] Release Activation 2.0.0-M1
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 not yet actively running the signature tests on the TomEE side. I propose we release 2.0.0-M1 so we have some non-snapshots to work with and come back to 2.0.0 as things look 100% on all fronts Staging Maven repository: - https://repository.apache.org/content/repositories/orgapachegeronimo-1153/ The only change is conversion from javax to the jakarta namespace via contributor Richard Zowalla. Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Abstain (please provide specific comments) [ ] -1 Don't approve the release (please provide specific comments) This vote will be open for at least 72 hours. -David smime.p7s Description: S/MIME cryptographic signature
