Re: Spark JIRA tags clarification and management

Yup I sometimes use it. I think quite a few others do. It might've been called out in the contributor guide too. On Thu, Sep 6, 2018 at 8:54 PM Sean Owen wrote: > I believe 'starter' is still the standard tag for simple issues for > newcomers. > > On Thu, Sep 6, 2018 at 8:46 PM Hyukjin Kwon wr

Re: Spark JIRA tags clarification and management

I believe 'starter' is still the standard tag for simple issues for newcomers. On Thu, Sep 6, 2018 at 8:46 PM Hyukjin Kwon wrote: > Does anyone know if we still user starter or newbie tags as well? >

Re: Spark JIRA tags clarification and management

om:Hyukjin Kwon > To:dev > Cc:Xiao Li , Wenchen Fan < > cloud0...@gmail.com> > Date:2018/09/04 14:20 > Subject:Re: Spark JIRA tags clarification and management > -- > > > > Thanks, Reynold. > > +

Re: Spark JIRA tags clarification and management

Of course, we would like to eliminate all of the following tags "flanky" or "flankytest" Kazuaki Ishizaki From: Hyukjin Kwon To: dev Cc: Xiao Li , Wenchen Fan Date: 2018/09/04 14:20 Subject: Re: Spark JIRA tags clarification and management Thank

Re: Spark JIRA tags clarification and management

idea. >>> There are a few for organizing but some also are critical to the release >>> process, like rel note. Would be good to clarify. >>> >>> -- >>> *From:* Reynold Xin >>> *Sent:* Sunday, September 2, 2018 11:50 PM &

Re: Spark JIRA tags clarification and management

September 2, 2018 11:50 PM >> *To:* Hyukjin Kwon >> *Cc:* dev >> *Subject:* Re: Spark JIRA tags clarification and management >> >> It would be great to document the common ones. >> >> On Sun, Sep 2, 2018 at 11:49 PM Hyukjin Kwon wrote: >> >&

Re: Spark JIRA tags clarification and management

cess, like rel note. Would be good to clarify. > > -- > *From:* Reynold Xin > *Sent:* Sunday, September 2, 2018 11:50 PM > *To:* Hyukjin Kwon > *Cc:* dev > *Subject:* Re: Spark JIRA tags clarification and management > > It would be great to do

Re: Spark JIRA tags clarification and management

+1 good idea. There are a few for organizing but some also are critical to the release process, like rel note. Would be good to clarify. From: Reynold Xin Sent: Sunday, September 2, 2018 11:50 PM To: Hyukjin Kwon Cc: dev Subject: Re: Spark JIRA tags

Re: Spark JIRA tags clarification and management

It would be great to document the common ones. On Sun, Sep 2, 2018 at 11:49 PM Hyukjin Kwon wrote: > Hi all, > > I lately noticed tags are often used to classify JIRAs. I was thinking we > better explicitly document what tags are used and explain which tag means > what. For instance, we document

Re: Spark JIRA Report

I don’t think that it makes sense to just close inactive JIRA issue without any human review.  There are many legitimate feature requests / bug reports that might be inactive for a long time because they’re low priorities to fix or because nobody has had time to deal with them yet. On December

Re: Spark JIRA Report

OK, that's good. Another approach we can take to controlling the number of stale JIRA issues is writing a bot that simply closes issues after N days of inactivity and prompts people to reopen the issue if it's still valid. I believe Sean Owen proposed that at one point (?). I wonder if that might

Re: Spark JIRA Report

Nick, Putting the N most stale issues into a report like your latest one does seem like a good way to tackle the wall of text effect that I'm worried about. On Sun, Dec 14, 2014 at 12:28 PM, Nicholas Chammas < nicholas.cham...@gmail.com> wrote: > Taking after Andrew’s suggestion, perhaps the rep

Re: Spark JIRA Report

Taking after Andrew’s suggestion, perhaps the report can just focus on Stale issues (no updates in > 90 days), since those are probably the easiest to act on. For example: Stale Issues

Re: Spark JIRA Report

I formatted this report using Markdown; I'm open to changing the structure or formatting or reducing the amount of information to make the report more easily consumable. Regarding just sending links or whether this would just be mailing list noise, those are a good questions. I've sent out links

Re: Spark JIRA Report

The goal of increasing visibility on open issues is a good one. How is this different from just a link to Jira though? Some might say this adds noise to the mailing list and doesn't contain any information not already available in Jira. The idea seems good but the formatting leaves a little to b

Re: Spark JIRA

Ok, will continue to work with the existing one for now. On Fri, Feb 28, 2014 at 11:36 AM, Josh Rosen wrote: > Apache INFRA has been trying to import our JIRA issues since June 2013: > https://issues.apache.org/jira/browse/INFRA-6419. It seems that JIRA > introduces minor import incompatibilitie

Re: Spark JIRA

Apache INFRA has been trying to import our JIRA issues since June 2013: https://issues.apache.org/jira/browse/INFRA-6419. It seems that JIRA introduces minor import incompatibilities with every update to JIRA OnDemand, so it's been a challenge to get the Apache and Atlasssian JIRA versions to sync

Re: Spark JIRA

I think they are working on it? https://issues.apache.org/jira/browse/SPARK Best, -- Nan Zhu On Friday, February 28, 2014 at 2:29 PM, Evan Chan wrote: > Hey guys, > > There is no plan to move the Spark JIRA from the current > https://spark-project.atlassian.net/ > > right? > > -- > -- >