Thanks for this hint, Alex.
I ran the following JQL to get some idea of our current status:
project in (lucene, solr) and "Attachment count" > 0 and status = Open
There were 1500 results.
1500. I couldn't believe it. This is a huge number of patches that are out
there.
I did a spot check, thinking that a lot of these might be bug reports with
error logs or screen shots attached, but nope. These are mostly patches.
I'm going to try starting with the oldest ones to see if they can be
rebase, have already been committed, or generally try to triage them. Would
appreciate any volunteers that want to help.
Mike
On Thu, Apr 27, 2017 at 3:21 PM, Alexandre Rafalovitch <arafa...@gmail.com>
wrote:
> There is an "Attachment count" filter, you can say it to be 1+. Not
> everything will be a patch, but it is a good first pass. It is under
> "More" dropdown.
>
> We also have some Github Integration fields in there, but they don't
> seem to be actually doing anything for Solr project.
>
> Regards,
> Alex.
> ----
> http://www.solr-start.com/ - Resources for Solr users, new and experienced
>
>
> On 27 April 2017 at 16:15, Mike Drob <md...@apache.org> wrote:
> > Devs,
> >
> > Does anybody have good JIRA filters or processes for finding issues with
> > patches available and attached, or maybe with open pull requests for
> them? I
> > was talking to a few folks and we remarked how patches can sometimes sit
> on
> > issues for a long time, and this seems like a wasted opportunity when it
> > happens.
> >
> > If the patch sits for too long, it can be discouraging to new
> contributors.
> > But it is also undesirable for us to let code rot happen like this, since
> > they may be fixes for bugs that we haven't run into ourselves yet.
> >
> > Other projects use a Jira "patch available" status, or rely mostly on
> GitHub
> > PRs, or have other mechanisms for improving visibility of pending
> > contributions. I don't know which method is best, and am curious what the
> > rest of the community thinks. Maybe this is already a solved issue.
> >
> > Mike
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
> For additional commands, e-mail: dev-h...@lucene.apache.org
>
>
