[
https://issues.apache.org/jira/browse/SPARK-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652290#comment-14652290
]
Sean Owen commented on SPARK-9568:
----------------------------------
I'm just picking on one of these [~rxin] but do these JIRAs add something over
the existing JIRAs plus Target Version? These "Foo for X.Y" umbrellas feel a
little redundant, and often don't get done for X.Y. In particular presumably
any change is tested to some degree before merging it so what would this
include? I can still imagine JIRAs to "add test coverage for X that never had
quite enough" of course but that's just a JIRA. I don't feel strongly about
this but am trying to figure out if we can use lighter, existing coordination
mechanisms first rather than create new ones.
> Spark MLlib 1.5.0 testing umbrella
> ----------------------------------
>
> Key: SPARK-9568
> URL: https://issues.apache.org/jira/browse/SPARK-9568
> Project: Spark
> Issue Type: Umbrella
> Components: MLlib
> Reporter: Reynold Xin
> Assignee: Xiangrui Meng
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
