Re: All Github PR closed

> > > BTW Here are the Mahout instructions: > http://mahout.apache.org/developers/github.html this would need to be > modified to use the “develop” branch strategy. It seems less than ideal but > is actually pretty easy in practice and much better than the purely Jira + > patch file method. > +1.

Re: All Github PR closed

> How do we reopen those PRs that were automatically closed? Can we committers > do that or should we ask the user to resubmit against the moved repo? If someone already on the org can't reopen we could ask infra to do it I suspect. > On Jul 4, 2016, at 11:16 AM, Pat Ferrel

Re: All Github PR closed

Yes, exactly what I was trying to explain. BTW even if I liked Jira and patch files, contributors have spoken in other projects and are far more likely to use a github PR when allowed to. How do we reopen those PRs that were automatically closed? Can we committers do that or should we ask the

Re: All Github PR closed

The way Mahout works is that committers can open or close PRs (though a github merge will fail). But I can’t re-poen these PRs. That would be an easy solution, right? Maybe someone just needs to grant us certain github permissions? On Jun 30, 2016, at 3:01 PM, Donald Szeto

Re: All Github PR closed

But not all PRs are closed, so it left me wondering if there is a set of conditions that were triggered when GitHub integration was turned on. On Thursday, June 30, 2016, Pat Ferrel wrote: > Maybe I missed the explanation but why are all the gitub PRs against the > PIO