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