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 <rmannibu...@gmail.com>: > > Le 6 déc. 2017 18:22, "Daniel Gruno" <humbed...@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 <humbed...@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 <johndam...@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 < > rmannibu...@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 <johndam...@apache.org>: >>>>>>> On Wed, Dec 6, 2017 at 11:00 AM Romain Manni-Bucau < >>>>>> rmannibu...@gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>>> 2017-12-06 16:41 GMT+01:00 sebb <seb...@gmail.com>: >>>>>>>>> On 6 December 2017 at 08:08, Reinhard Sandtner < > rsandt...@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-73330969d...@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-unsubscr...@incubator.apache.org >>>>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>>>> >>>>>>>> >>>>>>>> ------------------------------------------------------------ > --------- >>>>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>>>> >>>>>>>> >>>>>> >>>>>> --------------------------------------------------------------------- >>>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>>>> >>>>>> >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>>> For additional commands, e-mail: general-h...@incubator.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
