spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hari Shreedharan" <hshreedha...@cloudera.com>
Subject Re: Let's set Assignee for Fixed JIRAs
Date Fri, 24 Apr 2015 00:47:20 GMT
You’d need to add them as a contributor in the JIRA admin page. Once you do that, you should
be able to assign the jira to that person




Thanks, Hari

On Thu, Apr 23, 2015 at 5:33 PM, Shivaram Venkataraman
<shivaram@eecs.berkeley.edu> wrote:

> A related question that has affected me in the past: If we get a PR from a
> new developer I sometimes find that I am not able to assign an issue to
> them after merging the PR. Is there a process we need follow to get new
> contributors on to a particular group in JIRA ? Or does it somehow happen
> automatically ?
> Thanks
> Shivaram
> On Thu, Apr 23, 2015 at 5:26 PM, Sean Owen <sowen@cloudera.com> wrote:
>> Following my comment earlier that "I think we set Assignee for Fixed
>> JIRAs consistently", I found there are actually 880 counter examples.
>> Lots of them are old, and I'll try to fix as many that are recent (for
>> the 1.4.0 release credits) as I can stand to click through.
>>
>> Let's set Assignee after resolving consistently though. In various
>> ways I've heard that people do really like the bit of credit, and I
>> don't think anybody disputed setting Assignee *after* it was resolved
>> as a way of giving credit.
>>
>> People who know they're missing a credit are welcome to ping me
>> directly to get it fixed.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
>> For additional commands, e-mail: dev-help@spark.apache.org
>>
>>
Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message