Repository: spark
Updated Branches:
  refs/heads/master cfa397c12 -> 6abc45e34


[SPARK-5254][MLLIB] remove developers section from spark.ml guide

Forgot to remove this section in #4052.

Author: Xiangrui Meng <[email protected]>

Closes #4053 from mengxr/SPARK-5254-update and squashes the following commits:

f295bde [Xiangrui Meng] remove developers section from spark.ml guide


Project: http://git-wip-us.apache.org/repos/asf/spark/repo
Commit: http://git-wip-us.apache.org/repos/asf/spark/commit/6abc45e3
Tree: http://git-wip-us.apache.org/repos/asf/spark/tree/6abc45e3
Diff: http://git-wip-us.apache.org/repos/asf/spark/diff/6abc45e3

Branch: refs/heads/master
Commit: 6abc45e340d3be5f07236adc104db5f8dda0d514
Parents: cfa397c
Author: Xiangrui Meng <[email protected]>
Authored: Wed Jan 14 18:54:17 2015 -0800
Committer: Xiangrui Meng <[email protected]>
Committed: Wed Jan 14 18:54:17 2015 -0800

----------------------------------------------------------------------
 docs/ml-guide.md | 14 --------------
 1 file changed, 14 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/spark/blob/6abc45e3/docs/ml-guide.md
----------------------------------------------------------------------
diff --git a/docs/ml-guide.md b/docs/ml-guide.md
index 88158fd..be178d7 100644
--- a/docs/ml-guide.md
+++ b/docs/ml-guide.md
@@ -689,17 +689,3 @@ Spark ML currently depends on MLlib and has the same 
dependencies.
 Please see the [MLlib Dependencies guide](mllib-guide.html#Dependencies) for 
more info.
 
 Spark ML also depends upon Spark SQL, but the relevant parts of Spark SQL do 
not bring additional dependencies.
-
-# Developers
-
-**Development plan**
-
-If all goes well, `spark.ml` will become the primary ML package at the time of 
the Spark 1.3 release.  Initially, simple wrappers will be used to port 
algorithms to `spark.ml`, but eventually, code will be moved to `spark.ml` and 
`spark.mllib` will be deprecated.
-
-**Advice to developers**
-
-During the next development cycle, new algorithms should be contributed to 
`spark.mllib`, but we welcome patches sent to either package.  If an algorithm 
is best expressed using the new API (e.g., feature transformers), we may ask 
for developers to use the new `spark.ml` API.
-Wrappers for old and new algorithms can be contributed to `spark.ml`.
-
-Users will be able to use algorithms from either of the two packages.  The 
main difficulty will be the differences in APIs between the two packages.
-


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to