You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Josh Rosen (JIRA)" <ji...@apache.org> on 2019/06/09 19:19:00 UTC
[jira] [Commented] (SPARK-27972) Move SQL migration guide to the
top level
[ https://issues.apache.org/jira/browse/SPARK-27972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16859538#comment-16859538 ]
Josh Rosen commented on SPARK-27972:
------------------------------------
This reminds me: we should probably link these guides from the spark.apache.org site's release notes pages! I've talked to a few folks who were unaware that these guides existed and linking them more prominently from the release page could really help with discoverability.
> Move SQL migration guide to the top level
> -----------------------------------------
>
> Key: SPARK-27972
> URL: https://issues.apache.org/jira/browse/SPARK-27972
> Project: Spark
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 3.0.0
> Reporter: Xiao Li
> Priority: Major
>
> Currently, only SQL and MLLib have the dedicated section for documenting behavior changes and breaking changes. We found these guides simplify the upgrade experience for end users.
> [https://spark.apache.org/docs/latest/sql-migration-guide.html]
> [https://spark.apache.org/docs/2.4.3/ml-guide.html#migration-guide]
> The other components can do similar things in the same doc. Here, we propose to combine the migration guides and move it to the top level. All the components can document their behavior changes in the same PR that introduced the changes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org