spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nicholas Chammas <nicholas.cham...@gmail.com>
Subject Re: JIRA + PR backlog
Date Thu, 06 Nov 2014 21:49:43 GMT
I think better tooling will make it much easier for committers to trim the
list of stale JIRA issues and PRs. Convenience enables action.

   - Spark PR Dashboard <https://spark-prs.appspot.com/>: Additional
   filters for stale PRs
   <https://github.com/databricks/spark-pr-dashboard/issues/1> or PRs
   waiting on committer response would be great.
   - Stale Spark JIRA issues
   <https://issues.apache.org/jira/issues/?filter=12329614&jql=project%20%3D%20SPARK%20AND%20resolution%20%3D%20Unresolved%20AND%20updated%20%3C%3D%20-90d%20ORDER%20BY%20updated%20ASC>:
   This filter is sorted by the least recently updated issues first and can be
   filtered additionally by component. There are many, many easy wins in this
   filter.

Nick
‚Äč

On Thu, Nov 6, 2014 at 7:13 AM, Sean Owen <sowen@cloudera.com> wrote:

> (Different topic, indulge me one more reply --)
>
> Yes the number of JIRAs/PRs closed is unprecedented too and that
> deserves big praise. The project has stuck to making all changes and
> discussion in this public process, which is so powerful. Adjusted for
> the sheer inbound volume, Spark is doing a much better job than other
> projects; I would not hold them up as a benchmark of 'good enough', to
> be honest.
>
> JIRA is usually under-managed and it's a pet issue of mine. My motive
> is that core contributor / committer time is very valuable and in
> short supply. On the one hand we could use lots more of it to shepherd
> changes and fix bugs in the core that only the very experienced can.
> On the other hand, you all deserve time to work on your own changes,
> build a business, etc.
>
> So I harp on JIRA management as a way to save time:
> - Merging PRs sooner means less rebasing / retesting
> - Bouncing back bad PRs/JIRAs early teaches everyone what's acceptable
> as a good PR/JIRA and prevents the noise in the first place
> - Resolving issues soon prevents duplicates from being filed
> - Recording 'WontFix' resolutions early heads off repeated
> discussion/work on out of scope topics
>
> I have more concrete ideas about managing this but it's not for now.
> For now, thanks for zapping some old JIRAs this morning and for
> endorsing the idea of staying on top of the issue list in general. As
> a long-time fan I hope I can help from the sidelines by also closing
> JIRAs I'm all but certain are stale, and review minor PRs to clear the
> way for maintainers to take on the more important work.
>
>
> On Thu, Nov 6, 2014 at 7:21 AM, Matei Zaharia <matei.zaharia@gmail.com>
> wrote:
> > Several people asked about having maintainers review the PR queue for
> their modules regularly, and I like that idea. We have a new tool now to
> help with that in https://spark-prs.appspot.com.
> >
> > In terms of the set of open PRs itself, it is large but note that there
> are also 2800 *closed* PRs, which means we close the majority of PRs (and I
> don't know the exact stats but I'd guess that 90% of those are accepted and
> merged). I think one problem is that with GitHub, people often develop
> something as a PR and have a lot of discussion on there (including whether
> we even want the feature). I recently updated our "how to contribute" page
> to encourage opening a JIRA and having discussions on the dev list first,
> but I do think we need to be faster with closing ones that we don't have a
> plan to merge. Note that Hadoop, Hive, HBase, etc also have about 300
> issues each in the "patch available" state, so this is some kind of
> universal constant :P.
>
> ---------------------------------------------------------------------
> 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