You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@batchee.apache.org by Reinhard Sandtner <rs...@apache.org> on 2017/12/06 08:08:53 UTC
[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:
https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
the RESULT VOTE thread can be found here:
https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
For information about the contents of this release, see:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
The tag is available on my github fork
https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
Staging Repo is here:
https://repository.apache.org/content/repositories/orgapachebatchee-1005 <https://repository.apache.org/content/repositories/orgapachebatchee-1005>
Sources can be found here:
https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip <https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
Release artifacts are singed with the KEY:
https://github.com/apache/incubator-batchee/blob/master/KEYS <https://github.com/apache/incubator-batchee/blob/master/KEYS>
The vote is open for 72 hours
[ ] +1 batchEE -> coolShipIt()
[ ] +0 don’t care
[ ] -1 do not release because…
thanks, lg
reini
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 <rm...@gmail.com>:
>
> Le 6 déc. 2017 18:22, "Daniel Gruno" <hu...@apache.org> a écrit :
>
> On 12/06/2017 06:18 PM, Romain Manni-Bucau wrote:
>> 2017-12-06 18:14 GMT+01:00 Daniel Gruno <hu...@apache.org>:
>>>> 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.
>>>
>>> Move to gitbox, problem solved?
>>
>> Doesn't change anything AFAIK since it is the exact same archi no?
>
> No it's not the same architecture - that wouldn't make much sense :)
> gitbox is github r/w access with pruning of deleted branches enabled.
>
>
> Not sure I get whay it changes here and you can still not push a tag on the
> mainstream repo until it is vote*d*.
>
>
>>
>>> It strikes me as highly irregular that you are voting on something with
>>> no guaranteed provenance in place. Perhaps this is based on
>>> misinformation? I'd be inclined to vote -1 here, but I just can't be
>>> bothered.
>>
>> No guarantee is quite rude since it is still mainly about trust
>> between asf people. Or is the issue to use github only?
>
> It's not all about trust, it's trust BUT verify. We can verify on the
> ASF side, we can't verify someone's private repository. I'd also point
> to the incubator policy (as john linked to) that states that the source
> must be at ASF for a release vote to be held. Arguably, this is not the
> case here. I'd suggest you simply move the repos to gitbox, give us
> sufficient provenance to vote on the release, and you get to delete
> branches.
>
>
> We vote on the zip sources so this works.
>
> Side note: im not against gitbox but topic should move to batchee dev@ ;)
>
>
>
>>
>>>
>>>> That's the reason why we do NOT push the staging branch to the ASF
> cannonical repo. Never did for most ASF projects.
>>>> You can also read this up in the original GIT documentation I worked
> out with Infra and CouchDB.
>>>>
>>>> LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>>>>>
>>>>> 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 <
> rmannibucau@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> @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 <jo...@apache.org>:
>>>>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>>>>>> rmannibucau@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <
> rsandtner@apache.org>
>>>>>>>> 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
>>>>>>>> enhancements and extensions.
>>>>>>>>>>
>>>>>>>>>> You may find the VOTE thread here:
>>>>>>>>>>
>>>>>>>>
>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d
> 366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>>>>>> <
>>>>>>>>
>>>>>> http://mail-archives.apache.org/mod_mbox/batchee-dev/
> 201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>>>>>
>>>>>>>>
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
> 5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>>> <
>>>>>>>>
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
> 5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> For information about the contents of this release, see:
>>>>>>>>>>
>>>>>>>>
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314924&version=12334679
>>>>>>>> <
>>>>>>>>
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12314924&version=12334679
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> The tag is available on my github fork
>>>>>>>>>>
>>>>>>>>
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/
> batchee-0.5-incubating
>>>>>>>> <
>>>>>>>>
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/
> batchee-0.5-incubating
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> That does not seem right.
>>>>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>>>
>>>>>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>>>>>> ensure that they are permanent (naming convention hacks don't work
> so
>>>>>>>> using forks is the choice which has been done by several projects,
>>>>>>>> including BatchEE).
>>>>>>>>
>>>>>>>> If it helps I can push the tag on my fork (which would make it owned
>>>>>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>>>>>> here.
>>>>>>>>
>>>>>>>
>>>>>>> I think what we've been doing is pushing to the ASF repos and
> pointing to
>>>>>>> the specific commit hash.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Staging Repo is here:
>>>>>>>>>>
>>>>>>>>
>>>>>> https://repository.apache.org/content/repositories/
> orgapachebatchee-1005 <
>>>>>>>>
>>>>>> https://repository.apache.org/content/repositories/
> orgapachebatchee-1005>
>>>>>>>>>
>>>>>>>>> That is only the Maven staging area.
>>>>>>>>>
>>>>>>>>> The source must be released through the ASF mirror system,
>>>>>>>>>
>>>>>>>>> The staging area for that is here:
>>>>>>>>>
>>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>>>>
>>>>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>>>>
>>>>>>>>>> Sources can be found here:
>>>>>>>>>>
>>>>>>>>
>>>>>> https://repository.apache.org/content/repositories/
> orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
> incubating-source-release.zip
>>>>>>>> <
>>>>>>>>
>>>>>> https://repository.apache.org/content/repositories/
> orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
> incubating-source-release.zip
>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Release artifacts are singed with the KEY:
>>>>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>>>>
>>>>>>>>> The KEYS file must be under
>>>>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>>>>> hashes.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> The vote is open for 72 hours
>>>>>>>>>
>>>>>>>>> At least 72 hours.
>>>>>>>>>
>>>>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>>>>> [ ] +0 don’t care
>>>>>>>>>> [ ] -1 do not release because…
>>>>>>>>>>
>>>>>>>>>> thanks, lg
>>>>>>>>>> reini
>>>>>>>>>
>>>>>>>>> ------------------------------------------------------------
> ---------
>>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------
> ---------
>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 6 déc. 2017 18:22, "Daniel Gruno" <hu...@apache.org> a écrit :
On 12/06/2017 06:18 PM, Romain Manni-Bucau wrote:
> 2017-12-06 18:14 GMT+01:00 Daniel Gruno <hu...@apache.org>:
>> 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.
>>
>> Move to gitbox, problem solved?
>
> Doesn't change anything AFAIK since it is the exact same archi no?
No it's not the same architecture - that wouldn't make much sense :)
gitbox is github r/w access with pruning of deleted branches enabled.
Not sure I get whay it changes here and you can still not push a tag on the
mainstream repo until it is vote*d*.
>
>> It strikes me as highly irregular that you are voting on something with
>> no guaranteed provenance in place. Perhaps this is based on
>> misinformation? I'd be inclined to vote -1 here, but I just can't be
>> bothered.
>
> No guarantee is quite rude since it is still mainly about trust
> between asf people. Or is the issue to use github only?
It's not all about trust, it's trust BUT verify. We can verify on the
ASF side, we can't verify someone's private repository. I'd also point
to the incubator policy (as john linked to) that states that the source
must be at ASF for a release vote to be held. Arguably, this is not the
case here. I'd suggest you simply move the repos to gitbox, give us
sufficient provenance to vote on the release, and you get to delete
branches.
We vote on the zip sources so this works.
Side note: im not against gitbox but topic should move to batchee dev@ ;)
>
>>
>>> That's the reason why we do NOT push the staging branch to the ASF
cannonical repo. Never did for most ASF projects.
>>> You can also read this up in the original GIT documentation I worked
out with Infra and CouchDB.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>>>>
>>>> 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 <
rmannibucau@gmail.com>
>>>> wrote:
>>>>
>>>>> @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 <jo...@apache.org>:
>>>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>>>>> rmannibucau@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <
rsandtner@apache.org>
>>>>>>> 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
>>>>>>> enhancements and extensions.
>>>>>>>>>
>>>>>>>>> You may find the VOTE thread here:
>>>>>>>>>
>>>>>>>
>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d
366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>>>>> <
>>>>>>>
>>>>> http://mail-archives.apache.org/mod_mbox/batchee-dev/
201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>>>>
>>>>>>>>>
>>>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>>>>
>>>>>>>
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>> <
>>>>>>>
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>>>
>>>>>>>>>
>>>>>>>>> For information about the contents of this release, see:
>>>>>>>>>
>>>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12314924&version=12334679
>>>>>>> <
>>>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12314924&version=12334679
>>>>>>>>
>>>>>>>>>
>>>>>>>>> The tag is available on my github fork
>>>>>>>>>
>>>>>>>
>>>>> https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating
>>>>>>> <
>>>>>>>
>>>>> https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating
>>>>>>>>
>>>>>>>>
>>>>>>>> That does not seem right.
>>>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>>
>>>>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>>>>> ensure that they are permanent (naming convention hacks don't work
so
>>>>>>> using forks is the choice which has been done by several projects,
>>>>>>> including BatchEE).
>>>>>>>
>>>>>>> If it helps I can push the tag on my fork (which would make it owned
>>>>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>>>>> here.
>>>>>>>
>>>>>>
>>>>>> I think what we've been doing is pushing to the ASF repos and
pointing to
>>>>>> the specific commit hash.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Staging Repo is here:
>>>>>>>>>
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005 <
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005>
>>>>>>>>
>>>>>>>> That is only the Maven staging area.
>>>>>>>>
>>>>>>>> The source must be released through the ASF mirror system,
>>>>>>>>
>>>>>>>> The staging area for that is here:
>>>>>>>>
>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>>>
>>>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>>>
>>>>>>>>> Sources can be found here:
>>>>>>>>>
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
incubating-source-release.zip
>>>>>>> <
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
incubating-source-release.zip
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Release artifacts are singed with the KEY:
>>>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>>>
>>>>>>>> The KEYS file must be under
>>>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>>>> hashes.
>>>>>>>>
>>>>>>>>
>>>>>>>>> The vote is open for 72 hours
>>>>>>>>
>>>>>>>> At least 72 hours.
>>>>>>>>
>>>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>>>> [ ] +0 don’t care
>>>>>>>>> [ ] -1 do not release because…
>>>>>>>>>
>>>>>>>>> thanks, lg
>>>>>>>>> reini
>>>>>>>>
>>>>>>>> ------------------------------------------------------------
---------
>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ------------------------------------------------------------
---------
>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>
>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Daniel Gruno <hu...@apache.org>.
On 12/06/2017 06:18 PM, Romain Manni-Bucau wrote:
> 2017-12-06 18:14 GMT+01:00 Daniel Gruno <hu...@apache.org>:
>> 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.
>>
>> Move to gitbox, problem solved?
>
> Doesn't change anything AFAIK since it is the exact same archi no?
No it's not the same architecture - that wouldn't make much sense :)
gitbox is github r/w access with pruning of deleted branches enabled.
>
>> It strikes me as highly irregular that you are voting on something with
>> no guaranteed provenance in place. Perhaps this is based on
>> misinformation? I'd be inclined to vote -1 here, but I just can't be
>> bothered.
>
> No guarantee is quite rude since it is still mainly about trust
> between asf people. Or is the issue to use github only?
It's not all about trust, it's trust BUT verify. We can verify on the
ASF side, we can't verify someone's private repository. I'd also point
to the incubator policy (as john linked to) that states that the source
must be at ASF for a release vote to be held. Arguably, this is not the
case here. I'd suggest you simply move the repos to gitbox, give us
sufficient provenance to vote on the release, and you get to delete
branches.
>
>>
>>> That's the reason why we do NOT push the staging branch to the ASF cannonical repo. Never did for most ASF projects.
>>> You can also read this up in the original GIT documentation I worked out with Infra and CouchDB.
>>>
>>> LieGrue,
>>> strub
>>>
>>>
>>>> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>>>>
>>>> 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 <rm...@gmail.com>
>>>> wrote:
>>>>
>>>>> @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 <jo...@apache.org>:
>>>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>>>>> rmannibucau@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>>>>>>> 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
>>>>>>> enhancements and extensions.
>>>>>>>>>
>>>>>>>>> You may find the VOTE thread here:
>>>>>>>>>
>>>>>>>
>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>>>>> <
>>>>>>>
>>>>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>>>>
>>>>>>>>>
>>>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>>>>
>>>>>>>
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>> <
>>>>>>>
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>>>
>>>>>>>>>
>>>>>>>>> For information about the contents of this release, see:
>>>>>>>>>
>>>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>>> <
>>>>>>>
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>>>>
>>>>>>>>>
>>>>>>>>> The tag is available on my github fork
>>>>>>>>>
>>>>>>>
>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>>> <
>>>>>>>
>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>>>>
>>>>>>>>
>>>>>>>> That does not seem right.
>>>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>>
>>>>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>>>>> ensure that they are permanent (naming convention hacks don't work so
>>>>>>> using forks is the choice which has been done by several projects,
>>>>>>> including BatchEE).
>>>>>>>
>>>>>>> If it helps I can push the tag on my fork (which would make it owned
>>>>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>>>>> here.
>>>>>>>
>>>>>>
>>>>>> I think what we've been doing is pushing to the ASF repos and pointing to
>>>>>> the specific commit hash.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>> Staging Repo is here:
>>>>>>>>>
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>>>>
>>>>>>>> That is only the Maven staging area.
>>>>>>>>
>>>>>>>> The source must be released through the ASF mirror system,
>>>>>>>>
>>>>>>>> The staging area for that is here:
>>>>>>>>
>>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>>>
>>>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>>>
>>>>>>>>> Sources can be found here:
>>>>>>>>>
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>>> <
>>>>>>>
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Release artifacts are singed with the KEY:
>>>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>>>
>>>>>>>> The KEYS file must be under
>>>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>>>> hashes.
>>>>>>>>
>>>>>>>>
>>>>>>>>> The vote is open for 72 hours
>>>>>>>>
>>>>>>>> At least 72 hours.
>>>>>>>>
>>>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>>>> [ ] +0 don’t care
>>>>>>>>> [ ] -1 do not release because…
>>>>>>>>>
>>>>>>>>> thanks, lg
>>>>>>>>> reini
>>>>>>>>
>>>>>>>> ---------------------------------------------------------------------
>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>>
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>
>>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2017-12-06 18:14 GMT+01:00 Daniel Gruno <hu...@apache.org>:
> 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.
>
> Move to gitbox, problem solved?
Doesn't change anything AFAIK since it is the exact same archi no?
> It strikes me as highly irregular that you are voting on something with
> no guaranteed provenance in place. Perhaps this is based on
> misinformation? I'd be inclined to vote -1 here, but I just can't be
> bothered.
No guarantee is quite rude since it is still mainly about trust
between asf people. Or is the issue to use github only?
>
>> That's the reason why we do NOT push the staging branch to the ASF cannonical repo. Never did for most ASF projects.
>> You can also read this up in the original GIT documentation I worked out with Infra and CouchDB.
>>
>> LieGrue,
>> strub
>>
>>
>>> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>>>
>>> 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 <rm...@gmail.com>
>>> wrote:
>>>
>>>> @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 <jo...@apache.org>:
>>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>>>> rmannibucau@gmail.com>
>>>>> wrote:
>>>>>
>>>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>>>>>> 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
>>>>>> enhancements and extensions.
>>>>>>>>
>>>>>>>> You may find the VOTE thread here:
>>>>>>>>
>>>>>>
>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>>>> <
>>>>>>
>>>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>>>
>>>>>>>>
>>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>>>
>>>>>>
>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>> <
>>>>>>
>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>>
>>>>>>>>
>>>>>>>> For information about the contents of this release, see:
>>>>>>>>
>>>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>> <
>>>>>>
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>>>
>>>>>>>>
>>>>>>>> The tag is available on my github fork
>>>>>>>>
>>>>>>
>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>> <
>>>>>>
>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>>>
>>>>>>>
>>>>>>> That does not seem right.
>>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>
>>>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>>>> ensure that they are permanent (naming convention hacks don't work so
>>>>>> using forks is the choice which has been done by several projects,
>>>>>> including BatchEE).
>>>>>>
>>>>>> If it helps I can push the tag on my fork (which would make it owned
>>>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>>>> here.
>>>>>>
>>>>>
>>>>> I think what we've been doing is pushing to the ASF repos and pointing to
>>>>> the specific commit hash.
>>>>>
>>>>>
>>>>>>
>>>>>>>
>>>>>>>> Staging Repo is here:
>>>>>>>>
>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>>>
>>>>>>> That is only the Maven staging area.
>>>>>>>
>>>>>>> The source must be released through the ASF mirror system,
>>>>>>>
>>>>>>> The staging area for that is here:
>>>>>>>
>>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>>
>>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>>
>>>>>>>> Sources can be found here:
>>>>>>>>
>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>> <
>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>>>
>>>>>>>>
>>>>>>>> Release artifacts are singed with the KEY:
>>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>>
>>>>>>> The KEYS file must be under
>>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>>> hashes.
>>>>>>>
>>>>>>>
>>>>>>>> The vote is open for 72 hours
>>>>>>>
>>>>>>> At least 72 hours.
>>>>>>>
>>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>>> [ ] +0 don’t care
>>>>>>>> [ ] -1 do not release because…
>>>>>>>>
>>>>>>>> thanks, lg
>>>>>>>> reini
>>>>>>>
>>>>>>> ---------------------------------------------------------------------
>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>>
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Daniel Gruno <hu...@apache.org>.
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.
Move to gitbox, problem solved?
It strikes me as highly irregular that you are voting on something with
no guaranteed provenance in place. Perhaps this is based on
misinformation? I'd be inclined to vote -1 here, but I just can't be
bothered.
> That's the reason why we do NOT push the staging branch to the ASF cannonical repo. Never did for most ASF projects.
> You can also read this up in the original GIT documentation I worked out with Infra and CouchDB.
>
> LieGrue,
> strub
>
>
>> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>>
>> 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 <rm...@gmail.com>
>> wrote:
>>
>>> @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 <jo...@apache.org>:
>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>>> rmannibucau@gmail.com>
>>>> wrote:
>>>>
>>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>>>>> 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
>>>>> enhancements and extensions.
>>>>>>>
>>>>>>> You may find the VOTE thread here:
>>>>>>>
>>>>>
>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>>> <
>>>>>
>>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>>
>>>>>>>
>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>>
>>>>>
>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>> <
>>>>>
>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>>
>>>>>>>
>>>>>>> For information about the contents of this release, see:
>>>>>>>
>>>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>> <
>>>>>
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>>
>>>>>>>
>>>>>>> The tag is available on my github fork
>>>>>>>
>>>>>
>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>> <
>>>>>
>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>>
>>>>>>
>>>>>> That does not seem right.
>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>
>>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>>> ensure that they are permanent (naming convention hacks don't work so
>>>>> using forks is the choice which has been done by several projects,
>>>>> including BatchEE).
>>>>>
>>>>> If it helps I can push the tag on my fork (which would make it owned
>>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>>> here.
>>>>>
>>>>
>>>> I think what we've been doing is pushing to the ASF repos and pointing to
>>>> the specific commit hash.
>>>>
>>>>
>>>>>
>>>>>>
>>>>>>> Staging Repo is here:
>>>>>>>
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>>
>>>>>> That is only the Maven staging area.
>>>>>>
>>>>>> The source must be released through the ASF mirror system,
>>>>>>
>>>>>> The staging area for that is here:
>>>>>>
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>
>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>
>>>>>>> Sources can be found here:
>>>>>>>
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>> <
>>>>>
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>>
>>>>>>>
>>>>>>> Release artifacts are singed with the KEY:
>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>
>>>>>> The KEYS file must be under
>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>> hashes.
>>>>>>
>>>>>>
>>>>>>> The vote is open for 72 hours
>>>>>>
>>>>>> At least 72 hours.
>>>>>>
>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>> [ ] +0 don’t care
>>>>>>> [ ] -1 do not release because…
>>>>>>>
>>>>>>> thanks, lg
>>>>>>> reini
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 to the ASF cannonical repo. Never did for most ASF projects.
You can also read this up in the original GIT documentation I worked out with Infra and CouchDB.
LieGrue,
strub
> Am 06.12.2017 um 17:36 schrieb John D. Ament <jo...@apache.org>:
>
> 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 <rm...@gmail.com>
> wrote:
>
>> @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 <jo...@apache.org>:
>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
>> rmannibucau@gmail.com>
>>> wrote:
>>>
>>>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>>>> 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
>>>> enhancements and extensions.
>>>>>>
>>>>>> You may find the VOTE thread here:
>>>>>>
>>>>
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>>>> <
>>>>
>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>>>>>
>>>>>>
>>>>>> the RESULT VOTE thread can be found here:
>>>>>>
>>>>
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>> <
>>>>
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>>>>>
>>>>>>
>>>>>> For information about the contents of this release, see:
>>>>>>
>>>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>> <
>>>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>>>>>
>>>>>>
>>>>>> The tag is available on my github fork
>>>>>>
>>>>
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>> <
>>>>
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>>>>>
>>>>>
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>
>>>> During the vote - and for git - the tags shouldnt hit git@asf to
>>>> ensure that they are permanent (naming convention hacks don't work so
>>>> using forks is the choice which has been done by several projects,
>>>> including BatchEE).
>>>>
>>>> If it helps I can push the tag on my fork (which would make it owned
>>>> by the PMC) but since Reihard is a committer I don't see any issue
>>>> here.
>>>>
>>>
>>> I think what we've been doing is pushing to the ASF repos and pointing to
>>> the specific commit hash.
>>>
>>>
>>>>
>>>>>
>>>>>> Staging Repo is here:
>>>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>>>>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>
>>>>> That is only the Maven staging area.
>>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>>
>>>>> The staging area for that is here:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>
>>>>>> Sources can be found here:
>>>>>>
>>>>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>> <
>>>>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>>>>>
>>>>>>
>>>>>> Release artifacts are singed with the KEY:
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>> hashes.
>>>>>
>>>>>
>>>>>> The vote is open for 72 hours
>>>>>
>>>>> At least 72 hours.
>>>>>
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don’t care
>>>>>> [ ] -1 do not release because…
>>>>>>
>>>>>> thanks, lg
>>>>>> reini
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by "John D. Ament" <jo...@apache.org>.
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 <rm...@gmail.com>
wrote:
> @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 <jo...@apache.org>:
> > On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > wrote:
> >
> >> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> >> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
> >> 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
> >> enhancements and extensions.
> >> >>
> >> >> You may find the VOTE thread here:
> >> >>
> >>
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
> >> >
> >> >>
> >> >> the RESULT VOTE thread can be found here:
> >> >>
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >> <
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >> >
> >> >>
> >> >> For information about the contents of this release, see:
> >> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >> <
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >> >
> >> >>
> >> >> The tag is available on my github fork
> >> >>
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >> <
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >> >
> >> >
> >> > That does not seem right.
> >> > Tags need to be permanent and 'owned' by the (P)PMC
> >>
> >> During the vote - and for git - the tags shouldnt hit git@asf to
> >> ensure that they are permanent (naming convention hacks don't work so
> >> using forks is the choice which has been done by several projects,
> >> including BatchEE).
> >>
> >> If it helps I can push the tag on my fork (which would make it owned
> >> by the PMC) but since Reihard is a committer I don't see any issue
> >> here.
> >>
> >
> > I think what we've been doing is pushing to the ASF repos and pointing to
> > the specific commit hash.
> >
> >
> >>
> >> >
> >> >> Staging Repo is here:
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
> >> >
> >> > That is only the Maven staging area.
> >> >
> >> > The source must be released through the ASF mirror system,
> >> >
> >> > The staging area for that is here:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
> >> >
> >> > [If the vote succeeds, the files can be moved here:
> >> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
> >> >
> >> >> Sources can be found here:
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >> <
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >> >
> >> >>
> >> >> Release artifacts are singed with the KEY:
> >> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
> >> https://github.com/apache/incubator-batchee/blob/master/KEYS>
> >> >
> >> > The KEYS file must be under
> >> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> >> > hashes.
> >> >
> >> >
> >> >> The vote is open for 72 hours
> >> >
> >> > At least 72 hours.
> >> >
> >> >> [ ] +1 batchEE -> coolShipIt()
> >> >> [ ] +0 don’t care
> >> >> [ ] -1 do not release because…
> >> >>
> >> >> thanks, lg
> >> >> reini
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> > For additional commands, e-mail: general-help@incubator.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by "John D. Ament" <jo...@apache.org>.
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 <rm...@gmail.com>
wrote:
> @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 <jo...@apache.org>:
> > On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <
> rmannibucau@gmail.com>
> > wrote:
> >
> >> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> >> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
> >> 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
> >> enhancements and extensions.
> >> >>
> >> >> You may find the VOTE thread here:
> >> >>
> >>
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
> >> <
> >>
> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
> >> >
> >> >>
> >> >> the RESULT VOTE thread can be found here:
> >> >>
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >> <
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >> >
> >> >>
> >> >> For information about the contents of this release, see:
> >> >>
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >> <
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >> >
> >> >>
> >> >> The tag is available on my github fork
> >> >>
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >> <
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >> >
> >> >
> >> > That does not seem right.
> >> > Tags need to be permanent and 'owned' by the (P)PMC
> >>
> >> During the vote - and for git - the tags shouldnt hit git@asf to
> >> ensure that they are permanent (naming convention hacks don't work so
> >> using forks is the choice which has been done by several projects,
> >> including BatchEE).
> >>
> >> If it helps I can push the tag on my fork (which would make it owned
> >> by the PMC) but since Reihard is a committer I don't see any issue
> >> here.
> >>
> >
> > I think what we've been doing is pushing to the ASF repos and pointing to
> > the specific commit hash.
> >
> >
> >>
> >> >
> >> >> Staging Repo is here:
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
> >> >
> >> > That is only the Maven staging area.
> >> >
> >> > The source must be released through the ASF mirror system,
> >> >
> >> > The staging area for that is here:
> >> >
> >> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
> >> >
> >> > [If the vote succeeds, the files can be moved here:
> >> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
> >> >
> >> >> Sources can be found here:
> >> >>
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >> <
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >> >
> >> >>
> >> >> Release artifacts are singed with the KEY:
> >> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
> >> https://github.com/apache/incubator-batchee/blob/master/KEYS>
> >> >
> >> > The KEYS file must be under
> >> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> >> > hashes.
> >> >
> >> >
> >> >> The vote is open for 72 hours
> >> >
> >> > At least 72 hours.
> >> >
> >> >> [ ] +1 batchEE -> coolShipIt()
> >> >> [ ] +0 don’t care
> >> >> [ ] -1 do not release because…
> >> >>
> >> >> thanks, lg
> >> >> reini
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> > For additional commands, e-mail: general-help@incubator.apache.org
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> For additional commands, e-mail: general-help@incubator.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@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 <jo...@apache.org>:
> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>> 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
>> enhancements and extensions.
>> >>
>> >> You may find the VOTE thread here:
>> >>
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>> <
>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>> >
>> >>
>> >> the RESULT VOTE thread can be found here:
>> >>
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>> >
>> >>
>> >> For information about the contents of this release, see:
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>> >
>> >>
>> >> The tag is available on my github fork
>> >>
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>> <
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>> >
>> >
>> > That does not seem right.
>> > Tags need to be permanent and 'owned' by the (P)PMC
>>
>> During the vote - and for git - the tags shouldnt hit git@asf to
>> ensure that they are permanent (naming convention hacks don't work so
>> using forks is the choice which has been done by several projects,
>> including BatchEE).
>>
>> If it helps I can push the tag on my fork (which would make it owned
>> by the PMC) but since Reihard is a committer I don't see any issue
>> here.
>>
>
> I think what we've been doing is pushing to the ASF repos and pointing to
> the specific commit hash.
>
>
>>
>> >
>> >> Staging Repo is here:
>> >>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>> >
>> > That is only the Maven staging area.
>> >
>> > The source must be released through the ASF mirror system,
>> >
>> > The staging area for that is here:
>> >
>> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
>> >
>> > [If the vote succeeds, the files can be moved here:
>> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
>> >
>> >> Sources can be found here:
>> >>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>> <
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>> >
>> >>
>> >> Release artifacts are singed with the KEY:
>> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>> >
>> > The KEYS file must be under
>> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>> > hashes.
>> >
>> >
>> >> The vote is open for 72 hours
>> >
>> > At least 72 hours.
>> >
>> >> [ ] +1 batchEE -> coolShipIt()
>> >> [ ] +0 don’t care
>> >> [ ] -1 do not release because…
>> >>
>> >> thanks, lg
>> >> reini
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
@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 <jo...@apache.org>:
> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <rm...@gmail.com>
> wrote:
>
>> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
>> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
>> 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
>> enhancements and extensions.
>> >>
>> >> You may find the VOTE thread here:
>> >>
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
>> <
>> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
>> >
>> >>
>> >> the RESULT VOTE thread can be found here:
>> >>
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>> <
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
>> >
>> >>
>> >> For information about the contents of this release, see:
>> >>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>> <
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
>> >
>> >>
>> >> The tag is available on my github fork
>> >>
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>> <
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
>> >
>> >
>> > That does not seem right.
>> > Tags need to be permanent and 'owned' by the (P)PMC
>>
>> During the vote - and for git - the tags shouldnt hit git@asf to
>> ensure that they are permanent (naming convention hacks don't work so
>> using forks is the choice which has been done by several projects,
>> including BatchEE).
>>
>> If it helps I can push the tag on my fork (which would make it owned
>> by the PMC) but since Reihard is a committer I don't see any issue
>> here.
>>
>
> I think what we've been doing is pushing to the ASF repos and pointing to
> the specific commit hash.
>
>
>>
>> >
>> >> Staging Repo is here:
>> >>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>> >
>> > That is only the Maven staging area.
>> >
>> > The source must be released through the ASF mirror system,
>> >
>> > The staging area for that is here:
>> >
>> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
>> >
>> > [If the vote succeeds, the files can be moved here:
>> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
>> >
>> >> Sources can be found here:
>> >>
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>> <
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
>> >
>> >>
>> >> Release artifacts are singed with the KEY:
>> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
>> https://github.com/apache/incubator-batchee/blob/master/KEYS>
>> >
>> > The KEYS file must be under
>> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>> > hashes.
>> >
>> >
>> >> The vote is open for 72 hours
>> >
>> > At least 72 hours.
>> >
>> >> [ ] +1 batchEE -> coolShipIt()
>> >> [ ] +0 don’t care
>> >> [ ] -1 do not release because…
>> >>
>> >> thanks, lg
>> >> reini
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by "John D. Ament" <jo...@apache.org>.
On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
> 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
> enhancements and extensions.
> >>
> >> You may find the VOTE thread here:
> >>
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
> <
> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
> >
> >>
> >> the RESULT VOTE thread can be found here:
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> <
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >
> >>
> >> For information about the contents of this release, see:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >
> >>
> >> The tag is available on my github fork
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> <
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >
> >
> > That does not seem right.
> > Tags need to be permanent and 'owned' by the (P)PMC
>
> During the vote - and for git - the tags shouldnt hit git@asf to
> ensure that they are permanent (naming convention hacks don't work so
> using forks is the choice which has been done by several projects,
> including BatchEE).
>
> If it helps I can push the tag on my fork (which would make it owned
> by the PMC) but since Reihard is a committer I don't see any issue
> here.
>
I think what we've been doing is pushing to the ASF repos and pointing to
the specific commit hash.
>
> >
> >> Staging Repo is here:
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
> >
> > That is only the Maven staging area.
> >
> > The source must be released through the ASF mirror system,
> >
> > The staging area for that is here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
> >
> > [If the vote succeeds, the files can be moved here:
> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
> >
> >> Sources can be found here:
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> <
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >
> >>
> >> Release artifacts are singed with the KEY:
> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
> https://github.com/apache/incubator-batchee/blob/master/KEYS>
> >
> > The KEYS file must be under
> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> > hashes.
> >
> >
> >> The vote is open for 72 hours
> >
> > At least 72 hours.
> >
> >> [ ] +1 batchEE -> coolShipIt()
> >> [ ] +0 don’t care
> >> [ ] -1 do not release because…
> >>
> >> thanks, lg
> >> reini
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by "John D. Ament" <jo...@apache.org>.
On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau <rm...@gmail.com>
wrote:
> 2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> > On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
> 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
> enhancements and extensions.
> >>
> >> You may find the VOTE thread here:
> >>
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E
> <
> http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E
> >
> >>
> >> the RESULT VOTE thread can be found here:
> >>
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> <
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E
> >
> >>
> >> For information about the contents of this release, see:
> >>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> <
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679
> >
> >>
> >> The tag is available on my github fork
> >>
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> <
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating
> >
> >
> > That does not seem right.
> > Tags need to be permanent and 'owned' by the (P)PMC
>
> During the vote - and for git - the tags shouldnt hit git@asf to
> ensure that they are permanent (naming convention hacks don't work so
> using forks is the choice which has been done by several projects,
> including BatchEE).
>
> If it helps I can push the tag on my fork (which would make it owned
> by the PMC) but since Reihard is a committer I don't see any issue
> here.
>
I think what we've been doing is pushing to the ASF repos and pointing to
the specific commit hash.
>
> >
> >> Staging Repo is here:
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <
> https://repository.apache.org/content/repositories/orgapachebatchee-1005>
> >
> > That is only the Maven staging area.
> >
> > The source must be released through the ASF mirror system,
> >
> > The staging area for that is here:
> >
> > https://dist.apache.org/repos/dist/dev/incubator/batchee/
> >
> > [If the vote succeeds, the files can be moved here:
> > https://dist.apache.org/repos/dist/release/incubator/batchee/]
> >
> >> Sources can be found here:
> >>
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> <
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip
> >
> >>
> >> Release artifacts are singed with the KEY:
> >> https://github.com/apache/incubator-batchee/blob/master/KEYS <
> https://github.com/apache/incubator-batchee/blob/master/KEYS>
> >
> > The KEYS file must be under
> > https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> > hashes.
> >
> >
> >> The vote is open for 72 hours
> >
> > At least 72 hours.
> >
> >> [ ] +1 batchEE -> coolShipIt()
> >> [ ] +0 don’t care
> >> [ ] -1 do not release because…
> >>
> >> thanks, lg
> >> reini
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>
>> You may find the VOTE thread here:
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>
>> the RESULT VOTE thread can be found here:
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>
>> For information about the contents of this release, see:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>
>> The tag is available on my github fork
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>
> That does not seem right.
> Tags need to be permanent and 'owned' by the (P)PMC
During the vote - and for git - the tags shouldnt hit git@asf to
ensure that they are permanent (naming convention hacks don't work so
using forks is the choice which has been done by several projects,
including BatchEE).
If it helps I can push the tag on my fork (which would make it owned
by the PMC) but since Reihard is a committer I don't see any issue
here.
>
>> Staging Repo is here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>
> That is only the Maven staging area.
>
> The source must be released through the ASF mirror system,
>
> The staging area for that is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>
> [If the vote succeeds, the files can be moved here:
> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>
>> Sources can be found here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip <https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>
>> Release artifacts are singed with the KEY:
>> https://github.com/apache/incubator-batchee/blob/master/KEYS <https://github.com/apache/incubator-batchee/blob/master/KEYS>
>
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> hashes.
>
>
>> The vote is open for 72 hours
>
> At least 72 hours.
>
>> [ ] +1 batchEE -> coolShipIt()
>> [ ] +0 don’t care
>> [ ] -1 do not release because…
>>
>> thanks, lg
>> reini
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 10 December 2017 at 19:54, Mark Struberg <st...@yahoo.de.invalid> wrote:
>
>
>> Am 10.12.2017 um 13:30 schrieb sebb <se...@gmail.com>:
>>
>>>
>>> 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 aware off. If you commit a big zip to SVN, then the disc is consumed and will never get freed again.
I was told that they do have the means.
This is getting OT, but if that were a concern they would have made it
clear that dist/dev was only for RCs that were going to succeed.
Which would negate the point of providing dist/dev.
I don't believe Infra would have offered the service if they could not
handle deletions.
>>
>>> But it still would be a change to what we do in many TLPs since many years.
>>
>> Does not make it the best solution.
>>
>>> In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
>>> But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
>>> All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
>>>
>>> Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
>>> There was a good reason why we did get rid of that, you probably remember...
>>
>> The replacement for people/minotaur is precisely dist.apache.org.
>
> No, staging to people.a.o was faded out in ~2009 or 2010. And got replaced with repository.a.o.
repository.a.o is not used for non-Maven projects, nor does it release
non-Maven artefacts.
> dist.a.o only exists since around 2015 iirc
Yes, and dist.a.o is the replacement for ASF release staging which
used to happen using minotaur personal logins.
The release area was also on minotaur, so the process was to move
successful releases from the personal area to the release area.
The process now is much the same, except that dev and release are on
dist.a.o and use SVN for tracking.
>
>>
>>> Don't get me wrong: it's always good to review and discuss our release process.
>>> What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
>>> What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
>>
>> Indeed, but for projects with multiple release artifacts the dist/dev
>> URL plus revision number is shorter.
>> The dist/dev URL also makes it more obvious exactly what is planned to
>> be released to the ASF mirror system.
>> Wheres the parent dir for the source archive (*) includes files that
>> won't be published.
>>
>> (*) https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/
>
> If you don't have the exact hash then there is no guarantee (besides the word of the RM) that the packages in dist proper is the same as in dist/dev.
dist/dev and dist/release are in the same repo.
Since the RM uses SVN to copy/move the files from dev to release there
is full traceability back from release area to dev area revision to
VOTE mail.
> What is the scenario you want to guard us from? Release Managers who intentionally change source zips when moving from dist/dev or repository.a.o to dist proper?
No. RMs make mistakes.
> In that case the only thing which helps is a strong hash.
Not, so, see above - the dist/dev revision is sufficient.
> And if you trust the RM then both options are fine anyway.
Even trustworthy RMs make mistakes.
I think the dist/dev process is less error-prone.
Reviewers can see the files that are intended for the release area,
and the move to the release area is tracked through SVN.
> Sebb, can we finally please continue with the actual VOTE for BatchEE-0.5-incubating?
> It would be great if you could also take a look at the actual content.
> I know you are really good at spotting problems, so a review would be really welcome.
That is what this thread is all about, surely?
> txs and LieGrue,
> strub
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
> Am 10.12.2017 um 13:30 schrieb sebb <se...@gmail.com>:
>
>>
>> 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 aware off. If you commit a big zip to SVN, then the disc is consumed and will never get freed again.
>
>> But it still would be a change to what we do in many TLPs since many years.
>
> Does not make it the best solution.
But viable enough to _not_ kill a perfectly valid podling release!
>
>> In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
>> But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
>> All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
>>
>> Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
>> There was a good reason why we did get rid of that, you probably remember...
>
> The replacement for people/minotaur is precisely dist.apache.org.
No, staging to people.a.o was faded out in ~2009 or 2010. And got replaced with repository.a.o.
dist.a.o only exists since around 2015 iirc
>
>> Don't get me wrong: it's always good to review and discuss our release process.
>> What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
>> What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
>
> Indeed, but for projects with multiple release artifacts the dist/dev
> URL plus revision number is shorter.
> The dist/dev URL also makes it more obvious exactly what is planned to
> be released to the ASF mirror system.
> Wheres the parent dir for the source archive (*) includes files that
> won't be published.
>
> (*) https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/
If you don't have the exact hash then there is no guarantee (besides the word of the RM) that the packages in dist proper is the same as in dist/dev.
What is the scenario you want to guard us from? Release Managers who intentionally change source zips when moving from dist/dev or repository.a.o to dist proper?
In that case the only thing which helps is a strong hash. And if you trust the RM then both options are fine anyway.
Sebb, can we finally please continue with the actual VOTE for BatchEE-0.5-incubating?
It would be great if you could also take a look at the actual content.
I know you are really good at spotting problems, so a review would be really welcome.
txs and LieGrue,
strub
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
> Am 10.12.2017 um 13:30 schrieb sebb <se...@gmail.com>:
>
>>
>> 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 aware off. If you commit a big zip to SVN, then the disc is consumed and will never get freed again.
>
>> But it still would be a change to what we do in many TLPs since many years.
>
> Does not make it the best solution.
But viable enough to _not_ kill a perfectly valid podling release!
>
>> In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
>> But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
>> All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
>>
>> Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
>> There was a good reason why we did get rid of that, you probably remember...
>
> The replacement for people/minotaur is precisely dist.apache.org.
No, staging to people.a.o was faded out in ~2009 or 2010. And got replaced with repository.a.o.
dist.a.o only exists since around 2015 iirc
>
>> Don't get me wrong: it's always good to review and discuss our release process.
>> What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
>> What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
>
> Indeed, but for projects with multiple release artifacts the dist/dev
> URL plus revision number is shorter.
> The dist/dev URL also makes it more obvious exactly what is planned to
> be released to the ASF mirror system.
> Wheres the parent dir for the source archive (*) includes files that
> won't be published.
>
> (*) https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/
If you don't have the exact hash then there is no guarantee (besides the word of the RM) that the packages in dist proper is the same as in dist/dev.
What is the scenario you want to guard us from? Release Managers who intentionally change source zips when moving from dist/dev or repository.a.o to dist proper?
In that case the only thing which helps is a strong hash. And if you trust the RM then both options are fine anyway.
Sebb, can we finally please continue with the actual VOTE for BatchEE-0.5-incubating?
It would be great if you could also take a look at the actual content.
I know you are really good at spotting problems, so a review would be really welcome.
txs and LieGrue,
strub
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 10 December 2017 at 10:35, Mark Struberg <st...@yahoo.de.invalid> 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 repository.apache.org. Because all this is set up in the ASF own apache-parent pom.xml!
Or from target on the RM's system.
> You are indeed right in pointing out that the original vote mail should have added the sha1 of the source zip to vote on.
> Let's fix that:
> b51aebefc01e94f96df3d1a6664835524b855cf7
>
> But you are wrong by assuming that with dist/dev all would be perfect. Indeed, a SVN location is not worth much either if you don't know the _exact_ SVN revision!
> And this is missing in almost all votes as well.
Obviously one needs to include the revision number as well.
> By forcing dist/dev you basically render the staging area of repository.apache.org useless. You agree?
No, because the Maven artifacts need to reside there.
> 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.
> But it still would be a change to what we do in many TLPs since many years.
Does not make it the best solution.
> In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
> But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
> All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
>
> Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
> There was a good reason why we did get rid of that, you probably remember...
The replacement for people/minotaur is precisely dist.apache.org.
> Don't get me wrong: it's always good to review and discuss our release process.
> What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
> What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
Indeed, but for projects with multiple release artifacts the dist/dev
URL plus revision number is shorter.
The dist/dev URL also makes it more obvious exactly what is planned to
be released to the ASF mirror system.
Wheres the parent dir for the source archive (*) includes files that
won't be published.
(*) https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/
> Is this documented in the incubator release howto already?
>
> LieGrue,
> strub
>
>> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>>
>> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
>>> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
>>
>> 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.
>>
>>> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
>>
>> I don't understand how that can work, given the content of the VOTE mail.
>> Note that the Nexus repo URLs are transient and not version controlled AFAICT.
>> Nor are they unique as the numbers will eventually wrap.
>>
>> Try to use the SHA1 of any of the files in the previous release to
>> prove that the file is the one that was voted on.
>>
>> For example, under
>> www.apache.org/dist/incubator/batchee/0.4-incubating/
>> we have
>> batchee-0.4-incubating-source-release.zip.sha1
>> which contains
>> 05535de5554b598356f27bdb475853675b80b8b4
>>
>> The release vote is here:
>> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>>
>> How do you prove that the source zip is the one that was voted on?
>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>
>>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>>
>>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>>>
>>>>>> The source must be released through the ASF mirror system,
>>>>>> The source must be released through the ASF mirror system,
>>>>>> The staging area for that is here:
>>>>>
>>>>> That's also ONLY valid for AFTER the vote!
>>>>
>>>> No, the /dev/ area is the normal location for RCs
>>>>
>>>>> So once the VOTE passes we will copy it over.
>>>>
>>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>>
>>>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>>>
>>>> There have been changes over the years, including the introduction of
>>>> dist.apache.org.
>>>>
>>>> The point is to provide a staged copy of the release candidate under
>>>> /dev/ that reviewers can check.
>>>>
>>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>>
>>>> This then provides traceability from the vote to the /release/
>>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>>
>>>>>> The KEYS file must be under
>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>>>
>>>>> again AFTER the VOTE!
>>>>
>>>> The KEYS file can be updated at any time to include the RM's key.
>>>> It's vital that it is in place ready in case the vote succeeds.
>>>> So it makes sense to reference it in the VOTE email.
>>>>
>>>>> for the record: Romain and my votes are IPMC binding ones.
>>>>
>>>>> txs and LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>>
>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>>>
>>>>>>> You may find the VOTE thread here:
>>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>>
>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>>
>>>>>>> For information about the contents of this release, see:
>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>>
>>>>>>> The tag is available on my github fork
>>>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>>>
>>>>>> That does not seem right.
>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>
>>>>>>> Staging Repo is here:
>>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>>
>>>>>> That is only the Maven staging area.
>>>>>>
>>>>>> The source must be released through the ASF mirror system,
>>>>>>
>>>>>> The staging area for that is here:
>>>>>>
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>
>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>
>>>>>>> Sources can be found here:
>>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>>
>>>>>>> Release artifacts are singed with the KEY:
>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>
>>>>>> The KEYS file must be under
>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>> hashes.
>>>>>>
>>>>>>
>>>>>>> The vote is open for 72 hours
>>>>>>
>>>>>> At least 72 hours.
>>>>>>
>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>> [ ] +0 don’t care
>>>>>>> [ ] -1 do not release because…
>>>>>>>
>>>>>>> thanks, lg
>>>>>>> reini
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 10 déc. 2017 11:35, "Mark Struberg" <st...@yahoo.de.invalid> 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 repository.apache.org. Because all this is set up in
the ASF own apache-parent pom.xml!
You are indeed right in pointing out that the original vote mail should
have added the sha1 of the source zip to vote on.
Let's fix that:
b51aebefc01e94f96df3d1a6664835524b855cf7
But you are wrong by assuming that with dist/dev all would be perfect.
Indeed, a SVN location is not worth much either if you don't know the
_exact_ SVN revision!
And this is missing in almost all votes as well.
By forcing dist/dev you basically render the staging area of
repository.apache.org useless. You agree?
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. But it still would be a change to what
we do in many TLPs since many years.
In my personal opinion the dist/dev is a fine solution if the project does
not leverage a fully automated release build.
But for projects which use the maven-release-plugin doing a release is as
easy as mvn release:prepare + mvn release:perform.
All the rest is done automatically, including the deployment to a staging
area at repository.apache.org.
Forcing dist/dev for those projects would imo be more or less a step back
to deploying release candidates to people.a.o as we did a decade ago.
There was a good reason why we did get rid of that, you probably remember...
Don't get me wrong: it's always good to review and discuss our release
process.
What Reinhard did with the BatchEE release is really identical to what we
do in many TLPs.
What we really need to fix is the part with the sha1 (even better would be
sha256 though) as this is the only 100% way to ensure the VOTE is really on
the right source zip.
Exactly. Since the source is in the mvn closed staging repo with its hashes
it should also be fine OOTB.
Is this documented in the incubator release howto already?
Adding git.properties/svn.properties in the source at build time could even
remove any ambiguity.
Anyway this vote is regular so please proceed and open a new thread on the
process if there is really annissue please.
LieGrue,
strub
> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>
> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid>
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 operated territory.
>> The only thing which we must make sure is that the source zip get's
copied over to dist.a.o once the VOTE did succeed.
>
> 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.
>
>> And we have to ofc make sure that it is really the same as voted upon.
We ensure this via the sha1.
>
> I don't understand how that can work, given the content of the VOTE mail.
> Note that the Nexus repo URLs are transient and not version controlled
AFAICT.
> Nor are they unique as the numbers will eventually wrap.
>
> Try to use the SHA1 of any of the files in the previous release to
> prove that the file is the one that was voted on.
>
> For example, under
> www.apache.org/dist/incubator/batchee/0.4-incubating/
> we have
> batchee-0.4-incubating-source-release.zip.sha1
> which contains
> 05535de5554b598356f27bdb475853675b80b8b4
>
> The release vote is here:
> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567dd
ef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>
> How do you prove that the source zip is the one that was voted on?
>
>> txs and LieGrue,
>> strub
>>
>>
>>
>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid>
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 years
at the ASF.
>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>> The source must be released through the ASF mirror system,
>>>>> The staging area for that is here:
>>>>
>>>> That's also ONLY valid for AFTER the vote!
>>>
>>> No, the /dev/ area is the normal location for RCs
>>>
>>>> So once the VOTE passes we will copy it over.
>>>
>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>
>>>> Again: we handle it that way in TLPs and many podlings since MANY
years.
>>>
>>> There have been changes over the years, including the introduction of
>>> dist.apache.org.
>>>
>>> The point is to provide a staged copy of the release candidate under
>>> /dev/ that reviewers can check.
>>>
>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>
>>> This then provides traceability from the vote to the /release/
>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
hashes.
>>>>
>>>> again AFTER the VOTE!
>>>
>>> The KEYS file can be updated at any time to include the RM's key.
>>> It's vital that it is in place ready in case the vote succeeds.
>>> So it makes sense to reference it in the VOTE email.
>>>
>>>> for the record: Romain and my votes are IPMC binding ones.
>>>
>>>> txs and LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
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 enhancements and extensions.
>>>>>>
>>>>>> You may find the VOTE thread here:
>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d
366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <
http://mail-archives.apache.org/mod_mbox/batchee-dev/
201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>
>>>>>> the RESULT VOTE thread can be found here:
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <
https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>
>>>>>> For information about the contents of this release, see:
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12314924&version=12334679 <https://issues.apache.org/
jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>
>>>>>> The tag is available on my github fork
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating>
>>>>>
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>
>>>>>> Staging Repo is here:
>>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005<https://repository.apache.org/content/
repositories/orgapachebatchee-1005>
>>>>>
>>>>> That is only the Maven staging area.
>>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>>
>>>>> The staging area for that is here:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>
>>>>>> Sources can be found here:
>>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
incubating-source-release.zip<https://repository.apache.org/
content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-
incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>
>>>>>> Release artifacts are singed with the KEY:
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<
https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>> hashes.
>>>>>
>>>>>
>>>>>> The vote is open for 72 hours
>>>>>
>>>>> At least 72 hours.
>>>>>
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don’t care
>>>>>> [ ] -1 do not release because…
>>>>>>
>>>>>> thanks, lg
>>>>>> reini
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 10 December 2017 at 10:35, Mark Struberg <st...@yahoo.de.invalid> 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 repository.apache.org. Because all this is set up in the ASF own apache-parent pom.xml!
Or from target on the RM's system.
> You are indeed right in pointing out that the original vote mail should have added the sha1 of the source zip to vote on.
> Let's fix that:
> b51aebefc01e94f96df3d1a6664835524b855cf7
>
> But you are wrong by assuming that with dist/dev all would be perfect. Indeed, a SVN location is not worth much either if you don't know the _exact_ SVN revision!
> And this is missing in almost all votes as well.
Obviously one needs to include the revision number as well.
> By forcing dist/dev you basically render the staging area of repository.apache.org useless. You agree?
No, because the Maven artifacts need to reside there.
> 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.
> But it still would be a change to what we do in many TLPs since many years.
Does not make it the best solution.
> In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
> But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
> All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
>
> Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
> There was a good reason why we did get rid of that, you probably remember...
The replacement for people/minotaur is precisely dist.apache.org.
> Don't get me wrong: it's always good to review and discuss our release process.
> What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
> What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
Indeed, but for projects with multiple release artifacts the dist/dev
URL plus revision number is shorter.
The dist/dev URL also makes it more obvious exactly what is planned to
be released to the ASF mirror system.
Wheres the parent dir for the source archive (*) includes files that
won't be published.
(*) https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/
> Is this documented in the incubator release howto already?
>
> LieGrue,
> strub
>
>> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>>
>> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
>>> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
>>
>> 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.
>>
>>> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
>>
>> I don't understand how that can work, given the content of the VOTE mail.
>> Note that the Nexus repo URLs are transient and not version controlled AFAICT.
>> Nor are they unique as the numbers will eventually wrap.
>>
>> Try to use the SHA1 of any of the files in the previous release to
>> prove that the file is the one that was voted on.
>>
>> For example, under
>> www.apache.org/dist/incubator/batchee/0.4-incubating/
>> we have
>> batchee-0.4-incubating-source-release.zip.sha1
>> which contains
>> 05535de5554b598356f27bdb475853675b80b8b4
>>
>> The release vote is here:
>> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>>
>> How do you prove that the source zip is the one that was voted on?
>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>
>>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>>
>>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>>>
>>>>>> The source must be released through the ASF mirror system,
>>>>>> The source must be released through the ASF mirror system,
>>>>>> The staging area for that is here:
>>>>>
>>>>> That's also ONLY valid for AFTER the vote!
>>>>
>>>> No, the /dev/ area is the normal location for RCs
>>>>
>>>>> So once the VOTE passes we will copy it over.
>>>>
>>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>>
>>>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>>>
>>>> There have been changes over the years, including the introduction of
>>>> dist.apache.org.
>>>>
>>>> The point is to provide a staged copy of the release candidate under
>>>> /dev/ that reviewers can check.
>>>>
>>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>>
>>>> This then provides traceability from the vote to the /release/
>>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>>
>>>>>> The KEYS file must be under
>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>>>
>>>>> again AFTER the VOTE!
>>>>
>>>> The KEYS file can be updated at any time to include the RM's key.
>>>> It's vital that it is in place ready in case the vote succeeds.
>>>> So it makes sense to reference it in the VOTE email.
>>>>
>>>>> for the record: Romain and my votes are IPMC binding ones.
>>>>
>>>>> txs and LieGrue,
>>>>> strub
>>>>>
>>>>>
>>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>>
>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>>>
>>>>>>> You may find the VOTE thread here:
>>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>>
>>>>>>> the RESULT VOTE thread can be found here:
>>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>>
>>>>>>> For information about the contents of this release, see:
>>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>>
>>>>>>> The tag is available on my github fork
>>>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>>>
>>>>>> That does not seem right.
>>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>>
>>>>>>> Staging Repo is here:
>>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>>
>>>>>> That is only the Maven staging area.
>>>>>>
>>>>>> The source must be released through the ASF mirror system,
>>>>>>
>>>>>> The staging area for that is here:
>>>>>>
>>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>>
>>>>>> [If the vote succeeds, the files can be moved here:
>>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>>
>>>>>>> Sources can be found here:
>>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>>
>>>>>>> Release artifacts are singed with the KEY:
>>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>>
>>>>>> The KEYS file must be under
>>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>>> hashes.
>>>>>>
>>>>>>
>>>>>>> The vote is open for 72 hours
>>>>>>
>>>>>> At least 72 hours.
>>>>>>
>>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>>> [ ] +0 don’t care
>>>>>>> [ ] -1 do not release because…
>>>>>>>
>>>>>>> thanks, lg
>>>>>>> reini
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Le 10 déc. 2017 11:35, "Mark Struberg" <st...@yahoo.de.invalid> 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 repository.apache.org. Because all this is set up in
the ASF own apache-parent pom.xml!
You are indeed right in pointing out that the original vote mail should
have added the sha1 of the source zip to vote on.
Let's fix that:
b51aebefc01e94f96df3d1a6664835524b855cf7
But you are wrong by assuming that with dist/dev all would be perfect.
Indeed, a SVN location is not worth much either if you don't know the
_exact_ SVN revision!
And this is missing in almost all votes as well.
By forcing dist/dev you basically render the staging area of
repository.apache.org useless. You agree?
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. But it still would be a change to what
we do in many TLPs since many years.
In my personal opinion the dist/dev is a fine solution if the project does
not leverage a fully automated release build.
But for projects which use the maven-release-plugin doing a release is as
easy as mvn release:prepare + mvn release:perform.
All the rest is done automatically, including the deployment to a staging
area at repository.apache.org.
Forcing dist/dev for those projects would imo be more or less a step back
to deploying release candidates to people.a.o as we did a decade ago.
There was a good reason why we did get rid of that, you probably remember...
Don't get me wrong: it's always good to review and discuss our release
process.
What Reinhard did with the BatchEE release is really identical to what we
do in many TLPs.
What we really need to fix is the part with the sha1 (even better would be
sha256 though) as this is the only 100% way to ensure the VOTE is really on
the right source zip.
Exactly. Since the source is in the mvn closed staging repo with its hashes
it should also be fine OOTB.
Is this documented in the incubator release howto already?
Adding git.properties/svn.properties in the source at build time could even
remove any ambiguity.
Anyway this vote is regular so please proceed and open a new thread on the
process if there is really annissue please.
LieGrue,
strub
> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>
> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid>
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 operated territory.
>> The only thing which we must make sure is that the source zip get's
copied over to dist.a.o once the VOTE did succeed.
>
> 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.
>
>> And we have to ofc make sure that it is really the same as voted upon.
We ensure this via the sha1.
>
> I don't understand how that can work, given the content of the VOTE mail.
> Note that the Nexus repo URLs are transient and not version controlled
AFAICT.
> Nor are they unique as the numbers will eventually wrap.
>
> Try to use the SHA1 of any of the files in the previous release to
> prove that the file is the one that was voted on.
>
> For example, under
> www.apache.org/dist/incubator/batchee/0.4-incubating/
> we have
> batchee-0.4-incubating-source-release.zip.sha1
> which contains
> 05535de5554b598356f27bdb475853675b80b8b4
>
> The release vote is here:
> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567dd
ef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>
> How do you prove that the source zip is the one that was voted on?
>
>> txs and LieGrue,
>> strub
>>
>>
>>
>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid>
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 years
at the ASF.
>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>> The source must be released through the ASF mirror system,
>>>>> The staging area for that is here:
>>>>
>>>> That's also ONLY valid for AFTER the vote!
>>>
>>> No, the /dev/ area is the normal location for RCs
>>>
>>>> So once the VOTE passes we will copy it over.
>>>
>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>
>>>> Again: we handle it that way in TLPs and many podlings since MANY
years.
>>>
>>> There have been changes over the years, including the introduction of
>>> dist.apache.org.
>>>
>>> The point is to provide a staged copy of the release candidate under
>>> /dev/ that reviewers can check.
>>>
>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>
>>> This then provides traceability from the vote to the /release/
>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
hashes.
>>>>
>>>> again AFTER the VOTE!
>>>
>>> The KEYS file can be updated at any time to include the RM's key.
>>> It's vital that it is in place ready in case the vote succeeds.
>>> So it makes sense to reference it in the VOTE email.
>>>
>>>> for the record: Romain and my votes are IPMC binding ones.
>>>
>>>> txs and LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org>
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 enhancements and extensions.
>>>>>>
>>>>>> You may find the VOTE thread here:
>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d
366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <
http://mail-archives.apache.org/mod_mbox/batchee-dev/
201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>
>>>>>> the RESULT VOTE thread can be found here:
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <
https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c284
5fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>
>>>>>> For information about the contents of this release, see:
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
projectId=12314924&version=12334679 <https://issues.apache.org/
jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>
>>>>>> The tag is available on my github fork
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/
batchee-0.5-incubating>
>>>>>
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>
>>>>>> Staging Repo is here:
>>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005<https://repository.apache.org/content/
repositories/orgapachebatchee-1005>
>>>>>
>>>>> That is only the Maven staging area.
>>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>>
>>>>> The staging area for that is here:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>
>>>>>> Sources can be found here:
>>>>>> https://repository.apache.org/content/repositories/
orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-
incubating-source-release.zip<https://repository.apache.org/
content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-
incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>
>>>>>> Release artifacts are singed with the KEY:
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<
https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>> hashes.
>>>>>
>>>>>
>>>>>> The vote is open for 72 hours
>>>>>
>>>>> At least 72 hours.
>>>>>
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don’t care
>>>>>> [ ] -1 do not release because…
>>>>>>
>>>>>> thanks, lg
>>>>>> reini
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
> 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 are indeed right in pointing out that the original vote mail should have added the sha1 of the source zip to vote on.
Let's fix that:
b51aebefc01e94f96df3d1a6664835524b855cf7
But you are wrong by assuming that with dist/dev all would be perfect. Indeed, a SVN location is not worth much either if you don't know the _exact_ SVN revision!
And this is missing in almost all votes as well.
By forcing dist/dev you basically render the staging area of repository.apache.org useless. You agree?
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. But it still would be a change to what we do in many TLPs since many years.
In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
There was a good reason why we did get rid of that, you probably remember...
Don't get me wrong: it's always good to review and discuss our release process.
What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
Is this documented in the incubator release howto already?
LieGrue,
strub
> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>
> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
>> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
>
> 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.
>
>> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
>
> I don't understand how that can work, given the content of the VOTE mail.
> Note that the Nexus repo URLs are transient and not version controlled AFAICT.
> Nor are they unique as the numbers will eventually wrap.
>
> Try to use the SHA1 of any of the files in the previous release to
> prove that the file is the one that was voted on.
>
> For example, under
> www.apache.org/dist/incubator/batchee/0.4-incubating/
> we have
> batchee-0.4-incubating-source-release.zip.sha1
> which contains
> 05535de5554b598356f27bdb475853675b80b8b4
>
> The release vote is here:
> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>
> How do you prove that the source zip is the one that was voted on?
>
>> txs and LieGrue,
>> strub
>>
>>
>>
>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>> The source must be released through the ASF mirror system,
>>>>> The staging area for that is here:
>>>>
>>>> That's also ONLY valid for AFTER the vote!
>>>
>>> No, the /dev/ area is the normal location for RCs
>>>
>>>> So once the VOTE passes we will copy it over.
>>>
>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>
>>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>>
>>> There have been changes over the years, including the introduction of
>>> dist.apache.org.
>>>
>>> The point is to provide a staged copy of the release candidate under
>>> /dev/ that reviewers can check.
>>>
>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>
>>> This then provides traceability from the vote to the /release/
>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>>
>>>> again AFTER the VOTE!
>>>
>>> The KEYS file can be updated at any time to include the RM's key.
>>> It's vital that it is in place ready in case the vote succeeds.
>>> So it makes sense to reference it in the VOTE email.
>>>
>>>> for the record: Romain and my votes are IPMC binding ones.
>>>
>>>> txs and LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>>
>>>>>> You may find the VOTE thread here:
>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>
>>>>>> the RESULT VOTE thread can be found here:
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>
>>>>>> For information about the contents of this release, see:
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>
>>>>>> The tag is available on my github fork
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>>
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>
>>>>>> Staging Repo is here:
>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>
>>>>> That is only the Maven staging area.
>>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>>
>>>>> The staging area for that is here:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>
>>>>>> Sources can be found here:
>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>
>>>>>> Release artifacts are singed with the KEY:
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>> hashes.
>>>>>
>>>>>
>>>>>> The vote is open for 72 hours
>>>>>
>>>>> At least 72 hours.
>>>>>
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don’t care
>>>>>> [ ] -1 do not release because…
>>>>>>
>>>>>> thanks, lg
>>>>>> reini
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
> 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 are indeed right in pointing out that the original vote mail should have added the sha1 of the source zip to vote on.
Let's fix that:
b51aebefc01e94f96df3d1a6664835524b855cf7
But you are wrong by assuming that with dist/dev all would be perfect. Indeed, a SVN location is not worth much either if you don't know the _exact_ SVN revision!
And this is missing in almost all votes as well.
By forcing dist/dev you basically render the staging area of repository.apache.org useless. You agree?
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. But it still would be a change to what we do in many TLPs since many years.
In my personal opinion the dist/dev is a fine solution if the project does not leverage a fully automated release build.
But for projects which use the maven-release-plugin doing a release is as easy as mvn release:prepare + mvn release:perform.
All the rest is done automatically, including the deployment to a staging area at repository.apache.org.
Forcing dist/dev for those projects would imo be more or less a step back to deploying release candidates to people.a.o as we did a decade ago.
There was a good reason why we did get rid of that, you probably remember...
Don't get me wrong: it's always good to review and discuss our release process.
What Reinhard did with the BatchEE release is really identical to what we do in many TLPs.
What we really need to fix is the part with the sha1 (even better would be sha256 though) as this is the only 100% way to ensure the VOTE is really on the right source zip.
Is this documented in the incubator release howto already?
LieGrue,
strub
> Am 07.12.2017 um 15:01 schrieb sebb <se...@gmail.com>:
>
> On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
>> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
>
> 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.
>
>> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
>
> I don't understand how that can work, given the content of the VOTE mail.
> Note that the Nexus repo URLs are transient and not version controlled AFAICT.
> Nor are they unique as the numbers will eventually wrap.
>
> Try to use the SHA1 of any of the files in the previous release to
> prove that the file is the one that was voted on.
>
> For example, under
> www.apache.org/dist/incubator/batchee/0.4-incubating/
> we have
> batchee-0.4-incubating-source-release.zip.sha1
> which contains
> 05535de5554b598356f27bdb475853675b80b8b4
>
> The release vote is here:
> https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
>
> How do you prove that the source zip is the one that was voted on?
>
>> txs and LieGrue,
>> strub
>>
>>
>>
>>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>> The source must be released through the ASF mirror system,
>>>>> The staging area for that is here:
>>>>
>>>> That's also ONLY valid for AFTER the vote!
>>>
>>> No, the /dev/ area is the normal location for RCs
>>>
>>>> So once the VOTE passes we will copy it over.
>>>
>>> Once the vote passes you SVN copy/move /dev/ to /release/
>>>
>>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>>
>>> There have been changes over the years, including the introduction of
>>> dist.apache.org.
>>>
>>> The point is to provide a staged copy of the release candidate under
>>> /dev/ that reviewers can check.
>>>
>>> Ideally also provide the SVN revision of the folder in the vote email.
>>>
>>> This then provides traceability from the vote to the /release/
>>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>>
>>>> again AFTER the VOTE!
>>>
>>> The KEYS file can be updated at any time to include the RM's key.
>>> It's vital that it is in place ready in case the vote succeeds.
>>> So it makes sense to reference it in the VOTE email.
>>>
>>>> for the record: Romain and my votes are IPMC binding ones.
>>>
>>>> txs and LieGrue,
>>>> strub
>>>>
>>>>
>>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>>
>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>>
>>>>>> You may find the VOTE thread here:
>>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>>
>>>>>> the RESULT VOTE thread can be found here:
>>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>>
>>>>>> For information about the contents of this release, see:
>>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>>
>>>>>> The tag is available on my github fork
>>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>>
>>>>> That does not seem right.
>>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>>
>>>>>> Staging Repo is here:
>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>>
>>>>> That is only the Maven staging area.
>>>>>
>>>>> The source must be released through the ASF mirror system,
>>>>>
>>>>> The staging area for that is here:
>>>>>
>>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>>
>>>>> [If the vote succeeds, the files can be moved here:
>>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>>
>>>>>> Sources can be found here:
>>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>>
>>>>>> Release artifacts are singed with the KEY:
>>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>>
>>>>> The KEYS file must be under
>>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>>> hashes.
>>>>>
>>>>>
>>>>>> The vote is open for 72 hours
>>>>>
>>>>> At least 72 hours.
>>>>>
>>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>>> [ ] +0 don’t care
>>>>>> [ ] -1 do not release because…
>>>>>>
>>>>>> thanks, lg
>>>>>> reini
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
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.
> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
I don't understand how that can work, given the content of the VOTE mail.
Note that the Nexus repo URLs are transient and not version controlled AFAICT.
Nor are they unique as the numbers will eventually wrap.
Try to use the SHA1 of any of the files in the previous release to
prove that the file is the one that was voted on.
For example, under
www.apache.org/dist/incubator/batchee/0.4-incubating/
we have
batchee-0.4-incubating-source-release.zip.sha1
which contains
05535de5554b598356f27bdb475853675b80b8b4
The release vote is here:
https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
How do you prove that the source zip is the one that was voted on?
> txs and LieGrue,
> strub
>
>
>
>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>
>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>
>>>> The source must be released through the ASF mirror system,
>>>> The source must be released through the ASF mirror system,
>>>> The staging area for that is here:
>>>
>>> That's also ONLY valid for AFTER the vote!
>>
>> No, the /dev/ area is the normal location for RCs
>>
>>> So once the VOTE passes we will copy it over.
>>
>> Once the vote passes you SVN copy/move /dev/ to /release/
>>
>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>
>> There have been changes over the years, including the introduction of
>> dist.apache.org.
>>
>> The point is to provide a staged copy of the release candidate under
>> /dev/ that reviewers can check.
>>
>> Ideally also provide the SVN revision of the folder in the vote email.
>>
>> This then provides traceability from the vote to the /release/
>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>
>>>> The KEYS file must be under
>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>
>>> again AFTER the VOTE!
>>
>> The KEYS file can be updated at any time to include the RM's key.
>> It's vital that it is in place ready in case the vote succeeds.
>> So it makes sense to reference it in the VOTE email.
>>
>>> for the record: Romain and my votes are IPMC binding ones.
>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>
>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>
>>>>> You may find the VOTE thread here:
>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>
>>>>> the RESULT VOTE thread can be found here:
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>
>>>>> For information about the contents of this release, see:
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>
>>>>> The tag is available on my github fork
>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>
>>>> That does not seem right.
>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>
>>>>> Staging Repo is here:
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>
>>>> That is only the Maven staging area.
>>>>
>>>> The source must be released through the ASF mirror system,
>>>>
>>>> The staging area for that is here:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>
>>>> [If the vote succeeds, the files can be moved here:
>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>
>>>>> Sources can be found here:
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>
>>>>> Release artifacts are singed with the KEY:
>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>
>>>> The KEYS file must be under
>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>> hashes.
>>>>
>>>>
>>>>> The vote is open for 72 hours
>>>>
>>>> At least 72 hours.
>>>>
>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>> [ ] +0 don’t care
>>>>> [ ] -1 do not release because…
>>>>>
>>>>> thanks, lg
>>>>> reini
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 7 December 2017 at 10:22, Mark Struberg <st...@yahoo.de.invalid> 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 operated territory.
> The only thing which we must make sure is that the source zip get's copied over to dist.a.o once the VOTE did succeed.
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.
> And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
I don't understand how that can work, given the content of the VOTE mail.
Note that the Nexus repo URLs are transient and not version controlled AFAICT.
Nor are they unique as the numbers will eventually wrap.
Try to use the SHA1 of any of the files in the previous release to
prove that the file is the one that was voted on.
For example, under
www.apache.org/dist/incubator/batchee/0.4-incubating/
we have
batchee-0.4-incubating-source-release.zip.sha1
which contains
05535de5554b598356f27bdb475853675b80b8b4
The release vote is here:
https://lists.apache.org/thread.html/fc112978fe7682a95189f9d14567ddef23bd2fc860bbce89903bf5c9@%3Cgeneral.incubator.apache.org%3E
How do you prove that the source zip is the one that was voted on?
> txs and LieGrue,
> strub
>
>
>
>> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>>
>> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>>
>>>> The source must be released through the ASF mirror system,
>>>> The source must be released through the ASF mirror system,
>>>> The staging area for that is here:
>>>
>>> That's also ONLY valid for AFTER the vote!
>>
>> No, the /dev/ area is the normal location for RCs
>>
>>> So once the VOTE passes we will copy it over.
>>
>> Once the vote passes you SVN copy/move /dev/ to /release/
>>
>>> Again: we handle it that way in TLPs and many podlings since MANY years.
>>
>> There have been changes over the years, including the introduction of
>> dist.apache.org.
>>
>> The point is to provide a staged copy of the release candidate under
>> /dev/ that reviewers can check.
>>
>> Ideally also provide the SVN revision of the folder in the vote email.
>>
>> This then provides traceability from the vote to the /release/
>> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>>
>>>> The KEYS file must be under
>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>>
>>> again AFTER the VOTE!
>>
>> The KEYS file can be updated at any time to include the RM's key.
>> It's vital that it is in place ready in case the vote succeeds.
>> So it makes sense to reference it in the VOTE email.
>>
>>> for the record: Romain and my votes are IPMC binding ones.
>>
>>> txs and LieGrue,
>>> strub
>>>
>>>
>>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>>
>>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>>
>>>>> You may find the VOTE thread here:
>>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>>
>>>>> the RESULT VOTE thread can be found here:
>>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>>
>>>>> For information about the contents of this release, see:
>>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>>
>>>>> The tag is available on my github fork
>>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>>
>>>> That does not seem right.
>>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>>
>>>>> Staging Repo is here:
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>>
>>>> That is only the Maven staging area.
>>>>
>>>> The source must be released through the ASF mirror system,
>>>>
>>>> The staging area for that is here:
>>>>
>>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>>
>>>> [If the vote succeeds, the files can be moved here:
>>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>>
>>>>> Sources can be found here:
>>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>>
>>>>> Release artifacts are singed with the KEY:
>>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>>
>>>> The KEYS file must be under
>>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>>> hashes.
>>>>
>>>>
>>>>> The vote is open for 72 hours
>>>>
>>>> At least 72 hours.
>>>>
>>>>> [ ] +1 batchEE -> coolShipIt()
>>>>> [ ] +0 don’t care
>>>>> [ ] -1 do not release because…
>>>>>
>>>>> thanks, lg
>>>>> reini
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 copied over to dist.a.o once the VOTE did succeed.
And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
txs and LieGrue,
strub
> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>
> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>
>>> The source must be released through the ASF mirror system,
>>> The source must be released through the ASF mirror system,
>>> The staging area for that is here:
>>
>> That's also ONLY valid for AFTER the vote!
>
> No, the /dev/ area is the normal location for RCs
>
>> So once the VOTE passes we will copy it over.
>
> Once the vote passes you SVN copy/move /dev/ to /release/
>
>> Again: we handle it that way in TLPs and many podlings since MANY years.
>
> There have been changes over the years, including the introduction of
> dist.apache.org.
>
> The point is to provide a staged copy of the release candidate under
> /dev/ that reviewers can check.
>
> Ideally also provide the SVN revision of the folder in the vote email.
>
> This then provides traceability from the vote to the /release/
> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>
>>> The KEYS file must be under
>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>
>> again AFTER the VOTE!
>
> The KEYS file can be updated at any time to include the RM's key.
> It's vital that it is in place ready in case the vote succeeds.
> So it makes sense to reference it in the VOTE email.
>
>> for the record: Romain and my votes are IPMC binding ones.
>
>> txs and LieGrue,
>> strub
>>
>>
>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>
>>>> You may find the VOTE thread here:
>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>
>>>> the RESULT VOTE thread can be found here:
>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>
>>>> For information about the contents of this release, see:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>
>>>> The tag is available on my github fork
>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>
>>> That does not seem right.
>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>
>>>> Staging Repo is here:
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>
>>> That is only the Maven staging area.
>>>
>>> The source must be released through the ASF mirror system,
>>>
>>> The staging area for that is here:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>
>>> [If the vote succeeds, the files can be moved here:
>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>
>>>> Sources can be found here:
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>
>>>> Release artifacts are singed with the KEY:
>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>
>>> The KEYS file must be under
>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>> hashes.
>>>
>>>
>>>> The vote is open for 72 hours
>>>
>>> At least 72 hours.
>>>
>>>> [ ] +1 batchEE -> coolShipIt()
>>>> [ ] +0 don’t care
>>>> [ ] -1 do not release because…
>>>>
>>>> thanks, lg
>>>> reini
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 copied over to dist.a.o once the VOTE did succeed.
And we have to ofc make sure that it is really the same as voted upon. We ensure this via the sha1.
txs and LieGrue,
strub
> Am 06.12.2017 um 23:16 schrieb sebb <se...@gmail.com>:
>
> On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>>
>>> The source must be released through the ASF mirror system,
>>> The source must be released through the ASF mirror system,
>>> The staging area for that is here:
>>
>> That's also ONLY valid for AFTER the vote!
>
> No, the /dev/ area is the normal location for RCs
>
>> So once the VOTE passes we will copy it over.
>
> Once the vote passes you SVN copy/move /dev/ to /release/
>
>> Again: we handle it that way in TLPs and many podlings since MANY years.
>
> There have been changes over the years, including the introduction of
> dist.apache.org.
>
> The point is to provide a staged copy of the release candidate under
> /dev/ that reviewers can check.
>
> Ideally also provide the SVN revision of the folder in the vote email.
>
> This then provides traceability from the vote to the /release/
> (assuming SVN is used to move/copy the files from /dev/ to /release/).
>
>>> The KEYS file must be under
>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>>
>> again AFTER the VOTE!
>
> The KEYS file can be updated at any time to include the RM's key.
> It's vital that it is in place ready in case the vote succeeds.
> So it makes sense to reference it in the VOTE email.
>
>> for the record: Romain and my votes are IPMC binding ones.
>
>> txs and LieGrue,
>> strub
>>
>>
>>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>>
>>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>>
>>>> You may find the VOTE thread here:
>>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>>
>>>> the RESULT VOTE thread can be found here:
>>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>>
>>>> For information about the contents of this release, see:
>>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>>
>>>> The tag is available on my github fork
>>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>>
>>> That does not seem right.
>>> Tags need to be permanent and 'owned' by the (P)PMC
>>>
>>>> Staging Repo is here:
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>>
>>> That is only the Maven staging area.
>>>
>>> The source must be released through the ASF mirror system,
>>>
>>> The staging area for that is here:
>>>
>>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>>
>>> [If the vote succeeds, the files can be moved here:
>>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>>
>>>> Sources can be found here:
>>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>>
>>>> Release artifacts are singed with the KEY:
>>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>>
>>> The KEYS file must be under
>>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>>> hashes.
>>>
>>>
>>>> The vote is open for 72 hours
>>>
>>> At least 72 hours.
>>>
>>>> [ ] +1 batchEE -> coolShipIt()
>>>> [ ] +0 don’t care
>>>> [ ] -1 do not release because…
>>>>
>>>> thanks, lg
>>>> reini
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>
>> The source must be released through the ASF mirror system,
>> The source must be released through the ASF mirror system,
>> The staging area for that is here:
>
> That's also ONLY valid for AFTER the vote!
No, the /dev/ area is the normal location for RCs
> So once the VOTE passes we will copy it over.
Once the vote passes you SVN copy/move /dev/ to /release/
> Again: we handle it that way in TLPs and many podlings since MANY years.
There have been changes over the years, including the introduction of
dist.apache.org.
The point is to provide a staged copy of the release candidate under
/dev/ that reviewers can check.
Ideally also provide the SVN revision of the folder in the vote email.
This then provides traceability from the vote to the /release/
(assuming SVN is used to move/copy the files from /dev/ to /release/).
>> The KEYS file must be under
>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>
> again AFTER the VOTE!
The KEYS file can be updated at any time to include the RM's key.
It's vital that it is in place ready in case the vote succeeds.
So it makes sense to reference it in the VOTE email.
> for the record: Romain and my votes are IPMC binding ones.
> txs and LieGrue,
> strub
>
>
>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>
>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>
>>> You may find the VOTE thread here:
>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>
>>> the RESULT VOTE thread can be found here:
>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>
>>> For information about the contents of this release, see:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>
>>> The tag is available on my github fork
>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>
>> That does not seem right.
>> Tags need to be permanent and 'owned' by the (P)PMC
>>
>>> Staging Repo is here:
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>
>> That is only the Maven staging area.
>>
>> The source must be released through the ASF mirror system,
>>
>> The staging area for that is here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>
>> [If the vote succeeds, the files can be moved here:
>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>
>>> Sources can be found here:
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>
>>> Release artifacts are singed with the KEY:
>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>
>> The KEYS file must be under
>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>> hashes.
>>
>>
>>> The vote is open for 72 hours
>>
>> At least 72 hours.
>>
>>> [ ] +1 batchEE -> coolShipIt()
>>> [ ] +0 don’t care
>>> [ ] -1 do not release because…
>>>
>>> thanks, lg
>>> reini
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 6 December 2017 at 17:06, Mark Struberg <st...@yahoo.de.invalid> 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 years at the ASF.
>
>> The source must be released through the ASF mirror system,
>> The source must be released through the ASF mirror system,
>> The staging area for that is here:
>
> That's also ONLY valid for AFTER the vote!
No, the /dev/ area is the normal location for RCs
> So once the VOTE passes we will copy it over.
Once the vote passes you SVN copy/move /dev/ to /release/
> Again: we handle it that way in TLPs and many podlings since MANY years.
There have been changes over the years, including the introduction of
dist.apache.org.
The point is to provide a staged copy of the release candidate under
/dev/ that reviewers can check.
Ideally also provide the SVN revision of the folder in the vote email.
This then provides traceability from the vote to the /release/
(assuming SVN is used to move/copy the files from /dev/ to /release/).
>> The KEYS file must be under
>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
>
> again AFTER the VOTE!
The KEYS file can be updated at any time to include the RM's key.
It's vital that it is in place ready in case the vote succeeds.
So it makes sense to reference it in the VOTE email.
> for the record: Romain and my votes are IPMC binding ones.
> txs and LieGrue,
> strub
>
>
>> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>>
>> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>>
>>> You may find the VOTE thread here:
>>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>>
>>> the RESULT VOTE thread can be found here:
>>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>>
>>> For information about the contents of this release, see:
>>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>>
>>> The tag is available on my github fork
>>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>>
>> That does not seem right.
>> Tags need to be permanent and 'owned' by the (P)PMC
>>
>>> Staging Repo is here:
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>>
>> That is only the Maven staging area.
>>
>> The source must be released through the ASF mirror system,
>>
>> The staging area for that is here:
>>
>> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>>
>> [If the vote succeeds, the files can be moved here:
>> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>>
>>> Sources can be found here:
>>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>>
>>> Release artifacts are singed with the KEY:
>>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>>
>> The KEYS file must be under
>> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
>> hashes.
>>
>>
>>> The vote is open for 72 hours
>>
>> At least 72 hours.
>>
>>> [ ] +1 batchEE -> coolShipIt()
>>> [ ] +0 don’t care
>>> [ ] -1 do not release because…
>>>
>>> thanks, lg
>>> reini
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 source must be released through the ASF mirror system,
> The staging area for that is here:
That's also ONLY valid for AFTER the vote!
So once the VOTE passes we will copy it over.
Again: we handle it that way in TLPs and many podlings since MANY years.
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
again AFTER the VOTE!
for the record: Romain and my votes are IPMC binding ones.
txs and LieGrue,
strub
> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>
> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>
>> You may find the VOTE thread here:
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>
>> the RESULT VOTE thread can be found here:
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>
>> For information about the contents of this release, see:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>
>> The tag is available on my github fork
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>
> That does not seem right.
> Tags need to be permanent and 'owned' by the (P)PMC
>
>> Staging Repo is here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>
> That is only the Maven staging area.
>
> The source must be released through the ASF mirror system,
>
> The staging area for that is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>
> [If the vote succeeds, the files can be moved here:
> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>
>> Sources can be found here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>
>> Release artifacts are singed with the KEY:
>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> hashes.
>
>
>> The vote is open for 72 hours
>
> At least 72 hours.
>
>> [ ] +1 batchEE -> coolShipIt()
>> [ ] +0 don’t care
>> [ ] -1 do not release because…
>>
>> thanks, lg
>> reini
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 source must be released through the ASF mirror system,
> The staging area for that is here:
That's also ONLY valid for AFTER the vote!
So once the VOTE passes we will copy it over.
Again: we handle it that way in TLPs and many podlings since MANY years.
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and hashes.
again AFTER the VOTE!
for the record: Romain and my votes are IPMC binding ones.
txs and LieGrue,
strub
> Am 06.12.2017 um 16:41 schrieb sebb <se...@gmail.com>:
>
> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>
>> You may find the VOTE thread here:
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>
>> the RESULT VOTE thread can be found here:
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>
>> For information about the contents of this release, see:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>
>> The tag is available on my github fork
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>
> That does not seem right.
> Tags need to be permanent and 'owned' by the (P)PMC
>
>> Staging Repo is here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005<https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>
> That is only the Maven staging area.
>
> The source must be released through the ASF mirror system,
>
> The staging area for that is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>
> [If the vote succeeds, the files can be moved here:
> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>
>> Sources can be found here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip<https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>
>> Release artifacts are singed with the KEY:
>> https://github.com/apache/incubator-batchee/blob/master/KEYS<https://github.com/apache/incubator-batchee/blob/master/KEYS>
>
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> hashes.
>
>
>> The vote is open for 72 hours
>
> At least 72 hours.
>
>> [ ] +1 batchEE -> coolShipIt()
>> [ ] +0 don’t care
>> [ ] -1 do not release because…
>>
>> thanks, lg
>> reini
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
2017-12-06 16:41 GMT+01:00 sebb <se...@gmail.com>:
> On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>>
>> You may find the VOTE thread here:
>> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>>
>> the RESULT VOTE thread can be found here:
>> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>>
>> For information about the contents of this release, see:
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>>
>> The tag is available on my github fork
>> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
>
> That does not seem right.
> Tags need to be permanent and 'owned' by the (P)PMC
During the vote - and for git - the tags shouldnt hit git@asf to
ensure that they are permanent (naming convention hacks don't work so
using forks is the choice which has been done by several projects,
including BatchEE).
If it helps I can push the tag on my fork (which would make it owned
by the PMC) but since Reihard is a committer I don't see any issue
here.
>
>> Staging Repo is here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <https://repository.apache.org/content/repositories/orgapachebatchee-1005>
>
> That is only the Maven staging area.
>
> The source must be released through the ASF mirror system,
>
> The staging area for that is here:
>
> https://dist.apache.org/repos/dist/dev/incubator/batchee/
>
> [If the vote succeeds, the files can be moved here:
> https://dist.apache.org/repos/dist/release/incubator/batchee/]
>
>> Sources can be found here:
>> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip <https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>>
>> Release artifacts are singed with the KEY:
>> https://github.com/apache/incubator-batchee/blob/master/KEYS <https://github.com/apache/incubator-batchee/blob/master/KEYS>
>
> The KEYS file must be under
> https://www.apache.org/dist/incubator/batchee/ as must the sigs and
> hashes.
>
>
>> The vote is open for 72 hours
>
> At least 72 hours.
>
>> [ ] +1 batchEE -> coolShipIt()
>> [ ] +0 don’t care
>> [ ] -1 do not release because…
>>
>> thanks, lg
>> reini
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>
> You may find the VOTE thread here:
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>
> the RESULT VOTE thread can be found here:
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>
> For information about the contents of this release, see:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>
> The tag is available on my github fork
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
That does not seem right.
Tags need to be permanent and 'owned' by the (P)PMC
> Staging Repo is here:
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <https://repository.apache.org/content/repositories/orgapachebatchee-1005>
That is only the Maven staging area.
The source must be released through the ASF mirror system,
The staging area for that is here:
https://dist.apache.org/repos/dist/dev/incubator/batchee/
[If the vote succeeds, the files can be moved here:
https://dist.apache.org/repos/dist/release/incubator/batchee/]
> Sources can be found here:
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip <https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>
> Release artifacts are singed with the KEY:
> https://github.com/apache/incubator-batchee/blob/master/KEYS <https://github.com/apache/incubator-batchee/blob/master/KEYS>
The KEYS file must be under
https://www.apache.org/dist/incubator/batchee/ as must the sigs and
hashes.
> The vote is open for 72 hours
At least 72 hours.
> [ ] +1 batchEE -> coolShipIt()
> [ ] +0 don’t care
> [ ] -1 do not release because…
>
> thanks, lg
> reini
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by sebb <se...@gmail.com>.
On 6 December 2017 at 08:08, Reinhard Sandtner <rs...@apache.org> 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 enhancements and extensions.
>
> You may find the VOTE thread here:
> https://lists.apache.org/thread.html/50c023e02cebcb61bc61aa2ea6112d366b1dba0db04c045b7c1b415b@%3Cdev.batchee.apache.org%3E <http://mail-archives.apache.org/mod_mbox/batchee-dev/201712.mbox/%3C501767C2-1220-41F1-A8F9-73330969DAF1@apache.org%3E>
>
> the RESULT VOTE thread can be found here:
> https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E <https://lists.apache.org/thread.html/6d05ea8439167e15d720d318c9c2845fbd134ae2967321e3b7540386@%3Cdev.batchee.apache.org%3E>
>
> For information about the contents of this release, see:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679 <https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12314924&version=12334679>
>
> The tag is available on my github fork
> https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating <https://github.com/rsandtner/incubator-batchee/tree/batchee-0.5-incubating>
That does not seem right.
Tags need to be permanent and 'owned' by the (P)PMC
> Staging Repo is here:
> https://repository.apache.org/content/repositories/orgapachebatchee-1005 <https://repository.apache.org/content/repositories/orgapachebatchee-1005>
That is only the Maven staging area.
The source must be released through the ASF mirror system,
The staging area for that is here:
https://dist.apache.org/repos/dist/dev/incubator/batchee/
[If the vote succeeds, the files can be moved here:
https://dist.apache.org/repos/dist/release/incubator/batchee/]
> Sources can be found here:
> https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip <https://repository.apache.org/content/repositories/orgapachebatchee-1005/org/apache/batchee/batchee/0.5-incubating/batchee-0.5-incubating-source-release.zip>
>
> Release artifacts are singed with the KEY:
> https://github.com/apache/incubator-batchee/blob/master/KEYS <https://github.com/apache/incubator-batchee/blob/master/KEYS>
The KEYS file must be under
https://www.apache.org/dist/incubator/batchee/ as must the sigs and
hashes.
> The vote is open for 72 hours
At least 72 hours.
> [ ] +1 batchEE -> coolShipIt()
> [ ] +0 don’t care
> [ ] -1 do not release because…
>
> thanks, lg
> reini
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 <je...@gmail.com>:
>
> Hi
>
> Long and interesting thread.
>
> +1
>
> Jean Louis
>
> Le mar. 12 déc. 2017 à 05:16, Justin Mclean <ju...@me.com> 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
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 <je...@gmail.com>:
>
> Hi
>
> Long and interesting thread.
>
> +1
>
> Jean Louis
>
> Le mar. 12 déc. 2017 à 05:16, Justin Mclean <ju...@me.com> 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
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Jean-Louis MONTEIRO <je...@gmail.com>.
Hi
Long and interesting thread.
+1
Jean Louis
Le mar. 12 déc. 2017 à 05:16, Justin Mclean <ju...@me.com> 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
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Justin Mclean <ju...@me.com>.
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-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Justin Mclean <ju...@me.com>.
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 probably should do is to review all the (c) IBM files and check where we did add some significant amount of work (surpassing the threshold of originality).
> For those files we should _additionally_ also add the (c) ASF to the headers imo. Not a biggie,
Not a biggie - you need significant changes before changing / adding an addition header but up to the PMC. See points 4/5 in [1]
> I think there is no need to add anything to LICENSE as they are ALv2 anyway.
See [2] it’s not required but recommended especially if it’s not ASF licensed.
Thanks,
Justin
1. https://www.apache.org/legal/src-headers.html#3party
2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Mark Struberg <st...@yahoo.de.INVALID>.
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 having open discussions on the batche dev lists and submitting patches. And ofc we are also perfectly fine to contribute back to their version!
But still it's not an official donation and Copyright grant to the ASF and thus we also should not remove the original Copyright headers [1].
All the rest (files with ASF headers) are initially developed here at BatchEE and fully from us.
What we probably should do is to review all the (c) IBM files and check where we did add some significant amount of work (surpassing the threshold of originality).
For those files we should _additionally_ also add the (c) ASF to the headers imo. Not a biggie, but should be done.
> IMO If the files with IBM copyright were donated to the ASF then the headers should be replaced with ASF headers. If that is not the case and they are 3rd party files that are bundled in an Batchee release then the IBM headers should stay and the LICENSE needs to make it clear when they come from.
I think there is no need to add anything to LICENSE as they are ALv2 anyway. And we already mention IBM in the NOTICE file. So this part is fine as wall afaict.
And txs for reviewing!
LieGrue,
strub
[1] https://www.apache.org/legal/src-headers.html
> Do not modify or remove any copyright notices or licenses within third-party works.
> Am 11.12.2017 um 08:30 schrieb Justin Mclean <ju...@classsoftware.com>:
>
> 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 know the history of your project so this could be perfectly fine, and I’m missing something, but again it makes it hard to review.
>
> Where those 450+ ASF header files not in the donation and have been created since? I can can also see that that repo above has a lengthy NOTICE file (although it seems to incorrectly mention the Apache license and testing license information so I’m not 100% what if anything needs to be propagated to your current NOTICE file). I can also see that files with IBM copyrights have been changed at Apache e.g. [1]
>
> IMO If the files with IBM copyright were donated to the ASF then the headers should be replaced with ASF headers. If that is not the case and they are 3rd party files that are bundled in an Batchee release then the IBM headers should stay and the LICENSE needs to make it clear when they come from.
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/incubator-batchee/commits/ff8bbbd195a27efdcc5cde8e383b9e3d39914a46/jbatch/src/main/java/org/apache/batchee/spi/PersistenceManagerService.java
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Justin Mclean <ju...@classsoftware.com>.
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 know the history of your project so this could be perfectly fine, and I’m missing something, but again it makes it hard to review.
Where those 450+ ASF header files not in the donation and have been created since? I can can also see that that repo above has a lengthy NOTICE file (although it seems to incorrectly mention the Apache license and testing license information so I’m not 100% what if anything needs to be propagated to your current NOTICE file). I can also see that files with IBM copyrights have been changed at Apache e.g. [1]
IMO If the files with IBM copyright were donated to the ASF then the headers should be replaced with ASF headers. If that is not the case and they are 3rd party files that are bundled in an Batchee release then the IBM headers should stay and the LICENSE needs to make it clear when they come from.
Thanks,
Justin
1. https://github.com/apache/incubator-batchee/commits/ff8bbbd195a27efdcc5cde8e383b9e3d39914a46/jbatch/src/main/java/org/apache/batchee/spi/PersistenceManagerService.java
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <ju...@classsoftware.com> a écrit :
> 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 there because the copyright line have been
> relocated. [1] The Apache header used for ASF project is also different to
> that used in external projects i.e. mentions contributor license
> agreements. If some of the headers haven't changed then it’s unclear if
> they were part of the donation or come from somewhere else. If they come
> from somewhere else then that bit of Apache licensed software may have a
> NOTICE file that would need to be looked at and parts possibly copied to
> your NOTICE file. So have 120 or so files with IBM headers makes it a
> little hard to review.
>
> Thanks,
> Justin
>
> 1. https://www.apache.org/legal/src-headers.html#headers
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Justin Mclean <ju...@classsoftware.com>.
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 there because the copyright line have been relocated. [1] The Apache header used for ASF project is also different to that used in external projects i.e. mentions contributor license agreements. If some of the headers haven't changed then it’s unclear if they were part of the donation or come from somewhere else. If they come from somewhere else then that bit of Apache licensed software may have a NOTICE file that would need to be looked at and parts possibly copied to your NOTICE file. So have 120 or so files with IBM headers makes it a little hard to review.
Thanks,
Justin
1. https://www.apache.org/legal/src-headers.html#headers
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Romain Manni-Bucau <rm...@gmail.com>.
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" <ju...@classsoftware.com> a écrit :
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 code?
If so does that other 3rd party code have NOTICE files?
What do other IPMC members think?
I checked:
- incubating in name
- hashes and signatures correct
- disclaimer exists
- LICENSE is missing a couple of things (see below)
- NOTICE looks good
- A number of files (120 or so ) are still "Copyright 2012 International
Business Machines Corp.” and don’t have ASF headers. I assume these files
were part of the donation from IBM and just been missed? Two examples [3][4]
- no binary files in release
- can compile from source
LICENSE is missing a couple of permissive licenses.
- bootstrap [1][2] . While this is the older Apache license of bootstrap
(so it's not required to be added to LICENSE), more recent versions are MIT
licensed so might be good to call that out in the LICENSE. Bootstrap also
contains MIT licensed normalize.css.
- MIT licensed JQuery [5] which also contains MIT licensed Sizzle.js
And a very minor thing I notice some dependancies files refer to ALv2 as
the “Apache Public License 2.0” - not GPL thankfully :-) e.g. [6] but I
assume this is auto generated.
Thanks,
Justin
1. batchee-0.5-incubating/gui/servlet/embedded/src/main/
resources/META-INF/resources/internal/batchee/css/bootstrap.min.3.0.0.css
2. batchee-0.5-incubating/gui/servlet/embedded/src/main/
resources/META-INF/resources/internal/batchee/js/bootstrap.min.3.0.0.js
3. batchee-0.5-incubating/jbatch/src/main/xsd/jobXML_1_0.xsd
4. batchee-0.5-incubating/jbatch/src/main/java/org/apache/
batchee/container/impl/controller/chunk/RetryHandler.java
5. batchee-0.5-incubating/gui/servlet/embedded/src/main/
resources/META-INF/resources/internal/batchee/js/jquery-2.0.3.min.js
6. ./tools/maven-plugin/target/classes/META-INF/DEPENDENCIES
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: [VOTE] Release of Apache BatchEE 0.5-incubating
Posted by Justin Mclean <ju...@classsoftware.com>.
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 code? If so does that other 3rd party code have NOTICE files?
What do other IPMC members think?
I checked:
- incubating in name
- hashes and signatures correct
- disclaimer exists
- LICENSE is missing a couple of things (see below)
- NOTICE looks good
- A number of files (120 or so ) are still "Copyright 2012 International Business Machines Corp.” and don’t have ASF headers. I assume these files were part of the donation from IBM and just been missed? Two examples [3][4]
- no binary files in release
- can compile from source
LICENSE is missing a couple of permissive licenses.
- bootstrap [1][2] . While this is the older Apache license of bootstrap (so it's not required to be added to LICENSE), more recent versions are MIT licensed so might be good to call that out in the LICENSE. Bootstrap also contains MIT licensed normalize.css.
- MIT licensed JQuery [5] which also contains MIT licensed Sizzle.js
And a very minor thing I notice some dependancies files refer to ALv2 as the “Apache Public License 2.0” - not GPL thankfully :-) e.g. [6] but I assume this is auto generated.
Thanks,
Justin
1. batchee-0.5-incubating/gui/servlet/embedded/src/main/resources/META-INF/resources/internal/batchee/css/bootstrap.min.3.0.0.css
2. batchee-0.5-incubating/gui/servlet/embedded/src/main/resources/META-INF/resources/internal/batchee/js/bootstrap.min.3.0.0.js
3. batchee-0.5-incubating/jbatch/src/main/xsd/jobXML_1_0.xsd
4. batchee-0.5-incubating/jbatch/src/main/java/org/apache/batchee/container/impl/controller/chunk/RetryHandler.java
5. batchee-0.5-incubating/gui/servlet/embedded/src/main/resources/META-INF/resources/internal/batchee/js/jquery-2.0.3.min.js
6. ./tools/maven-plugin/target/classes/META-INF/DEPENDENCIES
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org