You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by Sean Busbey <bu...@cloudera.com> on 2015/06/24 20:52:50 UTC

Github PRs

Hey folks,

Just noticed we have a number of outstanding pull requests on the github
mirror.

https://github.com/apache/hbase/pulls

Anyone know if we're set to get emails on dev@ when these open? Can we try
to get them taken care of, even if that just means pointing folks to JIRA?

-- 
Sean

Re: Github PRs

Posted by Ted Yu <yu...@gmail.com>.
+1 on what Sean said.

On Wed, Jun 24, 2015 at 12:45 PM, Sean Busbey <bu...@cloudera.com> wrote:

> So for now comments on each pointing folks to the contributor guide and
> jira would work, right?
>
> On Wed, Jun 24, 2015 at 2:09 PM, Andrew Purtell <an...@gmail.com>
> wrote:
>
> > I don't think we should accept PRs until we've discussed it and there is
> > consensus to do it. As you can see we are not set up with the necessary
> > integration to support that.
> >
> > Not sure how we can document better we don't currently care about our
> > GitHub mirrors, but that would be good.
> >
> >
> > > On Jun 24, 2015, at 11:52 AM, Sean Busbey <bu...@cloudera.com> wrote:
> > >
> > > Hey folks,
> > >
> > > Just noticed we have a number of outstanding pull requests on the
> github
> > > mirror.
> > >
> > > https://github.com/apache/hbase/pulls
> > >
> > > Anyone know if we're set to get emails on dev@ when these open? Can we
> > try
> > > to get them taken care of, even if that just means pointing folks to
> > JIRA?
> > >
> > > --
> > > Sean
> >
>
>
>
> --
> Sean
>

Re: Github PRs

Posted by Stack <st...@duboce.net>.
Spark put up own tooling to accommodate github pull requests.

I like idea of a bot saying go open a JIRA. We could ask INFRA to have mail
dump into our dev list?

St.Ack

On Wed, Jun 24, 2015 at 7:30 PM, 张铎 <pa...@gmail.com> wrote:

> How does spark make use of Github? Seems they only use PRs to accept
> patches but still use apache jira.
>
> And for now, set up a bot that automatically comments on new PR to tell the
> contributor open issue on apache jira?
>
> 2015-06-25 3:45 GMT+08:00 Sean Busbey <bu...@cloudera.com>:
>
> > So for now comments on each pointing folks to the contributor guide and
> > jira would work, right?
> >
> > On Wed, Jun 24, 2015 at 2:09 PM, Andrew Purtell <
> andrew.purtell@gmail.com>
> > wrote:
> >
> > > I don't think we should accept PRs until we've discussed it and there
> is
> > > consensus to do it. As you can see we are not set up with the necessary
> > > integration to support that.
> > >
> > > Not sure how we can document better we don't currently care about our
> > > GitHub mirrors, but that would be good.
> > >
> > >
> > > > On Jun 24, 2015, at 11:52 AM, Sean Busbey <bu...@cloudera.com>
> wrote:
> > > >
> > > > Hey folks,
> > > >
> > > > Just noticed we have a number of outstanding pull requests on the
> > github
> > > > mirror.
> > > >
> > > > https://github.com/apache/hbase/pulls
> > > >
> > > > Anyone know if we're set to get emails on dev@ when these open? Can
> we
> > > try
> > > > to get them taken care of, even if that just means pointing folks to
> > > JIRA?
> > > >
> > > > --
> > > > Sean
> > >
> >
> >
> >
> > --
> > Sean
> >
>

Re: Github PRs

Posted by 张铎 <pa...@gmail.com>.
How does spark make use of Github? Seems they only use PRs to accept
patches but still use apache jira.

And for now, set up a bot that automatically comments on new PR to tell the
contributor open issue on apache jira?

2015-06-25 3:45 GMT+08:00 Sean Busbey <bu...@cloudera.com>:

> So for now comments on each pointing folks to the contributor guide and
> jira would work, right?
>
> On Wed, Jun 24, 2015 at 2:09 PM, Andrew Purtell <an...@gmail.com>
> wrote:
>
> > I don't think we should accept PRs until we've discussed it and there is
> > consensus to do it. As you can see we are not set up with the necessary
> > integration to support that.
> >
> > Not sure how we can document better we don't currently care about our
> > GitHub mirrors, but that would be good.
> >
> >
> > > On Jun 24, 2015, at 11:52 AM, Sean Busbey <bu...@cloudera.com> wrote:
> > >
> > > Hey folks,
> > >
> > > Just noticed we have a number of outstanding pull requests on the
> github
> > > mirror.
> > >
> > > https://github.com/apache/hbase/pulls
> > >
> > > Anyone know if we're set to get emails on dev@ when these open? Can we
> > try
> > > to get them taken care of, even if that just means pointing folks to
> > JIRA?
> > >
> > > --
> > > Sean
> >
>
>
>
> --
> Sean
>

Re: Github PRs

Posted by Sean Busbey <bu...@cloudera.com>.
So for now comments on each pointing folks to the contributor guide and
jira would work, right?

On Wed, Jun 24, 2015 at 2:09 PM, Andrew Purtell <an...@gmail.com>
wrote:

> I don't think we should accept PRs until we've discussed it and there is
> consensus to do it. As you can see we are not set up with the necessary
> integration to support that.
>
> Not sure how we can document better we don't currently care about our
> GitHub mirrors, but that would be good.
>
>
> > On Jun 24, 2015, at 11:52 AM, Sean Busbey <bu...@cloudera.com> wrote:
> >
> > Hey folks,
> >
> > Just noticed we have a number of outstanding pull requests on the github
> > mirror.
> >
> > https://github.com/apache/hbase/pulls
> >
> > Anyone know if we're set to get emails on dev@ when these open? Can we
> try
> > to get them taken care of, even if that just means pointing folks to
> JIRA?
> >
> > --
> > Sean
>



-- 
Sean

Re: Github PRs

Posted by Andrew Purtell <an...@gmail.com>.
I don't think we should accept PRs until we've discussed it and there is consensus to do it. As you can see we are not set up with the necessary integration to support that. 

Not sure how we can document better we don't currently care about our GitHub mirrors, but that would be good. 


> On Jun 24, 2015, at 11:52 AM, Sean Busbey <bu...@cloudera.com> wrote:
> 
> Hey folks,
> 
> Just noticed we have a number of outstanding pull requests on the github
> mirror.
> 
> https://github.com/apache/hbase/pulls
> 
> Anyone know if we're set to get emails on dev@ when these open? Can we try
> to get them taken care of, even if that just means pointing folks to JIRA?
> 
> -- 
> Sean