[
https://issues.apache.org/jira/browse/SPARK-9568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652343#comment-14652343
]
Sean Owen commented on SPARK-9568:
----------------------------------
[~rxin] 6 of the subtasks for "MLlib 1.4 QA plan" aren't done :) I suppose it's
a bit orthogonal to how work is tracked for release X.Y, but my theory is one
easy list (Target Version = X.Y) that we all pay attention to is less likely to
leave work behind.
What should we do with that one by the way? "Audit MLlib Python API for 1.4" is
targeted for 1.5.0 for example. Good, but, is this working?
Should these Umbrellas block the release of 1.5.0? if not, what's their value
as "for 1.5.0"? If so, that's fine although we can already make any JIRA a
blocker for 1.5.0.
It's hard to feel strongly about something that is at worst superfluous but can
we make sure to track both these 1.5.0 Umbrellas and Target Version = 1.5.0
before a release, and maybe then we can get a better feel for whether it works
better this time.
> 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]
