Open pull request count is down to 254 right now from ~325 several weeks
ago.
Open JIRA count is down slightly to 1262 from a peak over ~1320.
Obviously, in the face of an ever faster and larger stream of contributions.
There's a real positive impact of JIRA being a little more meaningful, a
Open pull request count is down to 254 right now from ~325 several weeks
ago.
This great. Ideally, we need to get this down to 50 and keep it there.
Having so many open pull requests is just a bad signal to contributors. But
it will take some time to get there.
- 1+ Component
Sean, do you
As of right now, there are no more open JIRA issues without an assigned
component
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SPARK%20AND%20resolution%20%3D%20Unresolved%20AND%20component%20%3D%20EMPTY%20ORDER%20BY%20updated%20DESC!
Hurray!
[image: yay]
Thanks to Sean and others
I think we already have a YARN component.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SPARK%20AND%20component%20%3D%20YARN
I don't think JIRA allows it to be mandatory, but if it does, that
would be useful.
On Sat, Feb 7, 2015 at 5:08 PM, Nicholas Chammas
Oh derp, missed the YARN component.
JIRA, does allow admins to make fields mandatory:
https://confluence.atlassian.com/display/JIRA/Specifying+Field+Behavior#SpecifyingFieldBehavior-Makingafieldrequiredoroptional
Nick
On Sat Feb 07 2015 at 5:23:10 PM Patrick Wendell pwend...@gmail.com wrote:
By the way, isn't it possible to make the Component field mandatory when
people open new issues? Shouldn't we do that?
Btw Patrick, don't we need a YARN component? I think our JIRA components
should roughly match the components on the PR dashboard
https://spark-prs.appspot.com/.
Nick
On Fri Feb
Do we need some new components to be added to the JIRA project?
Like:
-
scheduler
-
YARN
- spark-submit
- …?
Nick
On Fri Feb 06 2015 at 10:50:41 AM Nicholas Chammas
nicholas.cham...@gmail.com wrote:
+9000 on cleaning up JIRA.
Thank you Sean for laying out some
Per Nick's suggestion I added two components:
1. Spark Submit
2. Spark Scheduler
I figured I would just add these since if we decide later we don't
want them, we can simply merge them into Spark Core.
On Fri, Feb 6, 2015 at 11:53 AM, Nicholas Chammas
nicholas.cham...@gmail.com wrote:
Do we
+1. Jira cleanup would be good. Please let me know if I can help in some way!
Thanks, Hari
On Fri, Feb 6, 2015 at 11:56 AM, Nicholas Chammas
nicholas.cham...@gmail.com wrote:
Do we need some new components to be added to the JIRA project?
Like:
-
scheduler
-
YARN
-
I've wasted no time in wielding the commit bit to complete a number of
small, uncontroversial changes. I wouldn't commit anything that didn't
already appear to have review, consensus and little risk, but please
let me know if anything looked a little too bold, so I can calibrate.
Anyway, I'd
JIRA updates don't go to this list, they go to iss...@spark.apache.org. I
don't think many are signed up for that list, and those that are probably
have a flood of emails anyway.
So I'd definitely be in favor of any JIRA cleanup that you're up for.
-Sandy
On Fri, Feb 6, 2015 at 6:45 AM, Sean
11 matches
Mail list logo
