spark-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r1651941 - /spark/site/docs/1.2.0/ml-guide.html
Date Thu, 15 Jan 2015 03:08:02 GMT
Author: meng
Date: Thu Jan 15 03:08:01 2015
New Revision: 1651941

remove developers section from guide (SPARK-5254)


Modified: spark/site/docs/1.2.0/ml-guide.html
--- spark/site/docs/1.2.0/ml-guide.html (original)
+++ spark/site/docs/1.2.0/ml-guide.html Thu Jan 15 03:08:01 2015
@@ -160,7 +160,6 @@ to <code></code>.</p>
   <li><a href="#dependencies">Dependencies</a></li>
-  <li><a href="#developers">Developers</a></li>
 <h1 id="main-concepts">Main Concepts</h1>
@@ -838,20 +837,6 @@ Please see the <a href="mllib-guide.html
 <p>Spark ML also depends upon Spark SQL, but the relevant parts of Spark SQL do not
bring additional dependencies.</p>
-<h1 id="developers">Developers</h1>
-<p><strong>Development plan</strong></p>
-<p>If all goes well, <code></code> 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 <code></code>, but eventually, code will be moved to <code></code>
and <code>spark.mllib</code> will be deprecated.</p>
-<p><strong>Advice to developers</strong></p>
-<p>During the next development cycle, new algorithms should be contributed to <code>spark.mllib</code>,
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 <code></code>
-Wrappers for old and new algorithms can be contributed to <code></code>.</p>
-<p>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.</p>
         </div> <!-- /container -->

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message