Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Closing the VOTE with the following binding IPMC votes: [+1]: Romain Manni-Bucau, Mark Struberg, Justin Mclean, Jean-Louis Monteiro txs to all who reviewed and voted! LieGrue, strub > Am 12.12.2017 um 07:28 schrieb Jean-Louis MONTEIRO : > > Hi > > Long and interesting

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi Long and interesting thread. +1 Jean Louis Le mar. 12 déc. 2017 à 05:16, Justin Mclean a écrit : > Hi, > > +1 (binding) > > Please make sure the license issues (i.e the missing licenses) are fixed > up for the next release. > > Thanks, > Justin >

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi, +1 (binding) Please make sure the license issues (i.e the missing licenses) are fixed up for the next release. Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands,

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi Mark, > IBM developed a JBatch RI at github. They didn't officially submit their > JBatch RI as podling but just gave us the OK to do a 'friendly fork’ Thanks for that that’s clarifies what going on and looks fine to me. Not easy to review without that context however :-) > What we

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi Justin! tldr; I think we are fine and it has been clarified when we started incubation. longer version: IBM developed a JBatch RI at github. They didn't officially submit their JBatch RI as podling but just gave us the OK to do a 'friendly fork'. IBM peeps even actively participate by

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi, > We didnt change the headers (see > https://github.com/WASdev/standards.jsr352.jbatch/blob/master/com.ibm.jbatch.container/src/main/java/com/ibm/jbatch/container/impl/RetryHandler.java). Then I’m slightly confused as you have 450+ files with ASF headers and 120+ with IBM ones. Now I don’t

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

We didnt change the headers (see https://github.com/WASdev/standards.jsr352.jbatch/blob/master/com.ibm.jbatch.container/src/main/java/com/ibm/jbatch/container/impl/RetryHandler.java). What would be a better mention in NOTICE? Le 11 déc. 2017 07:26, "Justin Mclean" a

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi, > The root NOTICE references the donation but files are under apache v2 > license anyway, even referencing IBM so should be good. OKish, perhaps, but given we’re taking about 120 or so files rather than just a couple so I think it would be better if it was fixed. The NOTICE statement is

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi Justin The root NOTICE references the donation but files are under apache v2 license anyway, even referencing IBM so should be good. Romain Le 11 déc. 2017 07:02, "Justin Mclean" a écrit : Hi, I’m not 100% sure I would vote +1 on this release due to possible

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi, I’m not 100% sure I would vote +1 on this release due to possible header issues (copyright IBM) and missing license information, but it’s probably in the “please fix for next release” category. Where these files with IBM headers a part of the donation or do they come from other 3rd party

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 10 December 2017 at 19:54, Mark Struberg wrote: > > >> Am 10.12.2017 um 13:30 schrieb sebb : >> >>> >>> And one more drawback is that ditching a failed release from SVN will _not_ >>> free the occupied storage. >>> That might or might not be an

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

> Am 10.12.2017 um 13:30 schrieb sebb : > >> >> And one more drawback is that ditching a failed release from SVN will _not_ >> free the occupied storage. >> That might or might not be an issue. > > Infra have ways of dealing with that if necessary. Hmm, no. Not that I'm

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 10 December 2017 at 10:35, Mark Struberg wrote: > >> If you put them under /dev/ for the vote, that makes it easier for the >> reviewer to see what is actually intended for the release area. > > Yes and no. Where do we get this zip from? > The answer is: from

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Le 10 déc. 2017 11:35, "Mark Struberg" a écrit : > If you put them under /dev/ for the vote, that makes it easier for the > reviewer to see what is actually intended for the release area. Yes and no. Where do we get this zip from? The answer is: from

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

> If you put them under /dev/ for the vote, that makes it easier for the > reviewer to see what is actually intended for the release area. Yes and no. Where do we get this zip from? The answer is: from repository.apache.org. Because all this is set up in the ASF own apache-parent pom.xml! You

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 7 December 2017 at 10:22, Mark Struberg wrote: > Hi Sebb! > > commits got pushed to the ASF repo > https://github.com/apache/incubator-batchee/commits/master > > And we clarified the dist question with Infra. > All is fine as repository.apache.org is ASF owned and

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Hi Sebb! commits got pushed to the ASF repo https://github.com/apache/incubator-batchee/commits/master And we clarified the dist question with Infra. All is fine as repository.apache.org is ASF owned and operated territory. The only thing which we must make sure is that the source zip get's

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 6 December 2017 at 17:06, Mark Struberg wrote: > No sebb, the tag does NOT need to be owned by the PPMC. > We just have to make sure that the tag gets moved over to ASF _AFTER_ the > vote is closed. > That's how GIT works and that's how we work with GIT since many

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Otr now. Gitbox just moves the problem one repo further. It does not help AnYthing for real downstream repos. Lg Strub Mit autocorrect gesendet > Am 06.12.2017 um 18:32 schrieb Romain Manni-Bucau : > > Le 6 déc. 2017 18:22, "Daniel Gruno" a écrit :

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Le 6 déc. 2017 18:22, "Daniel Gruno" a écrit : On 12/06/2017 06:18 PM, Romain Manni-Bucau wrote: > 2017-12-06 18:14 GMT+01:00 Daniel Gruno : >> On 12/06/2017 06:10 PM, Mark Struberg wrote: >>> As explained in the original GIT at ASF threads many years

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 12/06/2017 06:18 PM, Romain Manni-Bucau wrote: > 2017-12-06 18:14 GMT+01:00 Daniel Gruno : >> On 12/06/2017 06:10 PM, Mark Struberg wrote: >>> As explained in the original GIT at ASF threads many years ago: you cannot >>> easily get rid of a branch at ASF. >>> Even if we

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

2017-12-06 18:14 GMT+01:00 Daniel Gruno : > On 12/06/2017 06:10 PM, Mark Struberg wrote: >> As explained in the original GIT at ASF threads many years ago: you cannot >> easily get rid of a branch at ASF. >> Even if we force-push a delete it will _not_ get propagated

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 12/06/2017 06:10 PM, Mark Struberg wrote: > As explained in the original GIT at ASF threads many years ago: you cannot > easily get rid of a branch at ASF. > Even if we force-push a delete it will _not_ get propagated downstream and > would cause clashes if a release needs to be re-rolled.

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

As explained in the original GIT at ASF threads many years ago: you cannot easily get rid of a branch at ASF. Even if we force-push a delete it will _not_ get propagated downstream and would cause clashes if a release needs to be re-rolled. That's the reason why we do NOT push the staging branch

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

No sebb, the tag does NOT need to be owned by the PPMC. We just have to make sure that the tag gets moved over to ASF _AFTER_ the vote is closed. That's how GIT works and that's how we work with GIT since many years at the ASF. > The source must be released through the ASF mirror system, > The

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

Right, but the IPMC has general oversight and responsibilities for podlings. Our requirements for what goes into a release are at https://incubator.apache.org/policy/incubation.html#releases John On Wed, Dec 6, 2017 at 11:16 AM Romain Manni-Bucau wrote: > @John: depends

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

@John: depends the project. DeltaSpike, BatchEE and several others don't and it is fine IMHO. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-12-06 17:04 GMT+01:00 John D. Ament : > On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau wrote: > 2017-12-06 16:41 GMT+01:00 sebb : > > On 6 December 2017 at 08:08, Reinhard Sandtner > wrote: > >> Hey incubator PMCs, > >> > >> The Apache BatchEE community has voted and

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

2017-12-06 16:41 GMT+01:00 sebb : > On 6 December 2017 at 08:08, Reinhard Sandtner wrote: >> Hey incubator PMCs, >> >> The Apache BatchEE community has voted and approved the proposal to release >> Apache BatchEE 0.5-incubating. >> Apache BatchEE is a

Re: [VOTE] Release of Apache BatchEE 0.5-incubating

On 6 December 2017 at 08:08, Reinhard Sandtner wrote: > Hey incubator PMCs, > > The Apache BatchEE community has voted and approved the proposal to release > Apache BatchEE 0.5-incubating. > Apache BatchEE is a JBatch implementation (JSR-352) which provides many >

[VOTE] Release of Apache BatchEE 0.5-incubating

Hey incubator PMCs, The Apache BatchEE community has voted and approved the proposal to release Apache BatchEE 0.5-incubating. Apache BatchEE is a JBatch implementation (JSR-352) which provides many enhancements and extensions. You may find the VOTE thread here: