[
https://issues.apache.org/jira/browse/SPARK-14808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378302#comment-15378302
]
Joseph K. Bradley commented on SPARK-14808:
-------------------------------------------
I know this has come up before, and I like the spirit of what you're
suggesting. In practice, in the past, docs have been updated before releases,
though not before RCs.
For the short term, I'm going to break the tasks into critical and non-critical
parts, and I'll work on the critical ones now.
For the long term, IMO the best way to placate people on both sides of the
argument (about updating docs before or after a release) is for all committers
to be stricter about requiring doc updates right after doc-worthy changes are
made.
> Spark MLlib, GraphX, SparkR 2.0 QA umbrella
> -------------------------------------------
>
> Key: SPARK-14808
> URL: https://issues.apache.org/jira/browse/SPARK-14808
> Project: Spark
> Issue Type: Umbrella
> Components: Documentation, GraphX, ML, MLlib, SparkR
> Reporter: Joseph K. Bradley
> Assignee: Joseph K. Bradley
> Priority: Critical
>
> This JIRA lists tasks for the next Spark release's QA period for MLlib,
> GraphX, and SparkR.
> The list below gives an overview of what is involved, and the corresponding
> JIRA issues are linked below that.
> h2. API
> * Check binary API compatibility for Scala/Java
> * Audit new public APIs (from the generated html doc)
> ** Scala
> ** Java compatibility
> ** Python coverage
> ** R
> * Check Experimental, DeveloperApi tags
> h2. Algorithms and performance
> *Performance*
> * _List any other missing performance tests from spark-perf here_
> * perf-tests for transformers (SPARK-2838)
> * MultilayerPerceptron (SPARK-11911)
> h2. Documentation and example code
> * For new algorithms, create JIRAs for updating the user guide sections &
> examples
> * Update Programming Guide
> * Update website
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
