[
https://issues.apache.org/jira/browse/SPARK-23106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16340645#comment-16340645
]
Nick Pentreath commented on SPARK-23106:
----------------------------------------
Thanks [~bago.amirbekian]. However, running MiMa is not enough for this task,
since some PRs are merged that add MiMa exclusions. So typically, to be safe,
we would also double check the MiMa exclusions added for ML during the release
cycle, to ensure the exclusions are valid (i.e. false positives etc. most
commonly due to changes made to private classes that MiMa picks up but that are
not part of the public API).
> ML, Graph 2.3 QA: API: Binary incompatible changes
> --------------------------------------------------
>
> Key: SPARK-23106
> URL: https://issues.apache.org/jira/browse/SPARK-23106
> Project: Spark
> Issue Type: Sub-task
> Components: Documentation, GraphX, ML, MLlib
> Affects Versions: 2.3.0
> Reporter: Joseph K. Bradley
> Priority: Blocker
>
> Generate a list of binary incompatible changes using MiMa and create new
> JIRAs for issues found. Filter out false positives as needed.
> If you want to take this task, look at the analogous task from the previous
> release QA, and ping the Assignee for advice.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
