[ 
https://issues.apache.org/jira/browse/SPARK-20506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16012098#comment-16012098
 ] 

Nick Pentreath commented on SPARK-20506:
----------------------------------------

Hey [~josephkb] [~yanboliang] [~srowen] [~felixcheung] [~holdenk] - for the ML 
guide updates we always have just done "things that broke", "things that were 
deprecated" and "things that changed". Which is fine, but actually we never 
really highlight "what's new and cool".

What do you feel about amending the ML guide front page with "Highlights in 
this release" (or something similar) before the Migration Guide (or elsewhere 
on the front page, even at the top perhaps)? Here we could highlight the major 
new features added. So for example in 2.2, we have {{LinearSVC}} and 
{{Imputer}}, as well as parity progress on {{FPGrowth}}, stats methods and 
{{ALS}} to name a few.

I think it will be good to both make it easier for users to understand what is 
new and noteworthy, as well as a slightly more "positive" item instead of just 
"migration guide" :) 

> ML, Graph 2.2 QA: Programming guide update and migration guide
> --------------------------------------------------------------
>
>                 Key: SPARK-20506
>                 URL: https://issues.apache.org/jira/browse/SPARK-20506
>             Project: Spark
>          Issue Type: Sub-task
>          Components: Documentation, GraphX, ML, MLlib
>            Reporter: Joseph K. Bradley
>            Assignee: Nick Pentreath
>            Priority: Critical
>
> Before the release, we need to update the MLlib and GraphX Programming 
> Guides.  Updates will include:
> * Add migration guide subsection.
> ** Use the results of the QA audit JIRAs and [SPARK-17692].
> * Check phrasing, especially in main sections (for outdated items such as "In 
> this release, ...")



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to