Re: Branch deletion prohibited

Hi Brane, I hadn't joined the project back then, so I don't know the history, but my guess is that the loss of traceability might have occurred as a result of importing the code from an external repository. I don't see why they could be attributed to branch deletion – probably I'm not feeling

Re: Branch deletion prohibited

On 23.11.2015 04:13, Konstantin Boudnik wrote: > On Sun, Nov 22, 2015 at 02:16PM, Dmitriy Setrakyan wrote: >> Cos, >> >> I believe this is the ticket: >> https://issues.apache.org/jira/browse/INFRA-10798 >> >> This policy does seem myopic, would be great if Ignite could get an >> exemption. >

Re: Branch deletion prohibited

On 23.11.2015 20:41, Konstantin Boudnik wrote: > On Mon, Nov 23, 2015 at 09:08AM, Branko Čibej wrote: >> On 23.11.2015 04:13, Konstantin Boudnik wrote: >>> On Sun, Nov 22, 2015 at 02:16PM, Dmitriy Setrakyan wrote: Cos, I believe this is the ticket:

Re: Branch deletion prohibited

On Mon, Nov 23, 2015 at 08:02PM, Raul Kripalani wrote: > Hi Brane, > > I hadn't joined the project back then, so I don't know the history, but my > guess is that the loss of traceability might have occurred as a result of > importing the code from an external repository. I don't see why they

Re: Branch deletion prohibited

Raul is there are a ticket for this INFRA ticket? Sorry if I missed it... I regurgitate about this no-branch-delete policy imposed by a myopic "policy" considerations. And I want to increase the pressure on board@ for this sort of things. Would appreciate the pointer if exist. Thanks! Cos

Re: Branch deletion prohibited

Cos, I believe this is the ticket: https://issues.apache.org/jira/browse/INFRA-10798 This policy does seem myopic, would be great if Ignite could get an exemption. D. On Sun, Nov 22, 2015 at 11:58 AM, Konstantin Boudnik wrote: > Raul > > is there are a ticket for this INFRA

Re: Branch deletion prohibited

Exactly. Let's wait for Infra's feedback on why that restriction and when it'll be lifted.

Re: Branch deletion prohibited

Dmitriy, No, according to a note [1] on the wiki page [2] we need to check on unmerged changes before. Looks like we should add a status column (someone already has proposed it) where we can track is a branch ready to delete or not. [1] *Note. We don’t remove any *unmerged* branches. Even if the

Re: Branch deletion prohibited

Disagree. This means none but committer can contribute. --Yakov 2015-11-19 12:08 GMT+03:00 Raul Kripalani : > I disagree. > > Code should be in the ASF infra. > > Pull requests make sense when outsiders want to make contributions. > > The usage of ASF infra is not a mere

Re: Branch deletion prohibited

So branch deletion is disabled on purpose? On 19 Nov 2015 09:10, "Artem Shutak" wrote: > Dmitriy, > > No, according to a note [1] on the wiki page [2] we need to check on > unmerged changes before. Looks like we should add a status column (someone > already has proposed it)

Re: Branch deletion prohibited

Lads, It is not clear to me whether branch deletion is prohibited ASF-wide (Dmitriy: "we *cannot* delete branches") or by express project request. I've understood both things from the thread. So let's wait for INFRA to clarify: [1]. Can someone please explain why we resort to Github in the first

Re: Branch deletion prohibited

Should we file a ticket with INFRA asking them to delete all the branches listed on this page: https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete Is it safe? D. On Thu, Nov 19, 2015 at 12:57 AM, Yakov Zhdanov wrote: > Guys, therefore, let's

Re: Branch deletion prohibited

I disagree. Code should be in the ASF infra. Pull requests make sense when outsiders want to make contributions. The usage of ASF infra is not a mere formality. Raúl. On 19 Nov 2015 08:57, "Yakov Zhdanov" wrote: > Guys, therefore, let's develop new functionality in

Re: Branch deletion prohibited

On Thu, Nov 19, 2015 at 1:19 AM, Raul Kripalani wrote: > As I said: "Pull requests make sense when outsiders want to make > contributions." > > Committers with write access to ASF Git have no reason to develop > in Github. > Raul, given that we cannot delete branches, I think

Re: Branch deletion prohibited

I'd like to add that there is virtually no difference between using a branch in original repo and a branch in your personal fork on GitHub. Merges and other operations work seamlessly between multiple remotes. Committers don't even have to create PRs (except to run a TC build). Thanks, On Thu,

Re: Branch deletion prohibited

On Thu, Nov 19, 2015 at 1:41 AM, Raul Kripalani wrote: > On Thu, Nov 19, 2015 at 9:28 AM, Yakov Zhdanov > wrote: > > > But this leads to tons of garbage in repo and abandoned branches, etc. > > > > "Let's not do X because our developers are irresponsible

Re: Branch deletion prohibited

I agree that there is absolutely no problems of have multiple ways to provide contributions. If you are contributor, you can: - Provide a patch; - Provide a PR using GitHub mirror. If you are committer, you can: - Provide a patch; - Provide a PR using GitHub mirror; - Use branch in ASF repo and

Re: Branch deletion prohibited

As I said: "Pull requests make sense when outsiders want to make contributions." Committers with write access to ASF Git have no reason to develop in Github. On 19 Nov 2015 09:13, "Yakov Zhdanov" wrote: > Disagree. This means none but committer can contribute. > > --Yakov >

Re: Branch deletion prohibited

But this leads to tons of garbage in repo and abandoned branches, etc. --Yakov 2015-11-19 12:19 GMT+03:00 Raul Kripalani : > As I said: "Pull requests make sense when outsiders want to make > contributions." > > Committers with write access to ASF Git have no reason to develop

Re: Branch deletion prohibited

On Thu, Nov 19, 2015 at 9:28 AM, Yakov Zhdanov wrote: > But this leads to tons of garbage in repo and abandoned branches, etc. > "Let's not do X because our developers are irresponsible and leave branches behind?" -- Really? We have a zillion-pages set of contribution

Re: Branch deletion prohibited

Ok. So Infra replied and referred to an email on November 3rd which I somehow missed, indicating that it is indeed an ASF-wide temporary restriction. +1 to liberty of options to contribute/commit and to temporarily keeping track of branches to delete in the Wiki. Regards, *Raúl Kripalani* PMC &

Re: Branch deletion prohibited

+1 On Thu, Nov 19, 2015 at 1:07 PM, Vladimir Ozerov wrote: > I agree that there is absolutely no problems of have multiple ways to > provide contributions. > > If you are contributor, you can: > - Provide a patch; > - Provide a PR using GitHub mirror. > > If you are

Branch deletion prohibited

Fellows, I'm trying to push a branch deletion and the ASF Git tells me that branch deletion is prohibited. Has someone changed something? [raul@~/Workbench/Source/ignite$] git push -f origin :ignite-1790 remote: error: denying ref deletion for refs/heads/ignite-1790 To

Re: Branch deletion prohibited

Raul, ASF is currently prohibiting deletion of GIT branches until further notice. Please add your branch to this Wiki page, so we don’t loose track: https://cwiki.apache.org/confluence/display/IGNITE/Git+branches+to+delete Thanks, D. On Wed, Nov 18, 2015 at 10:16 AM, Raul Kripalani