[ 
https://issues.apache.org/jira/browse/SPARK-7537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joseph K. Bradley updated SPARK-7537:
-------------------------------------
    Description: 
Audit new public Scala APIs added to MLlib in 1.4.  Take note of:
* Protected/public classes or methods.  If access can be more private, then it 
should be.
* Documentation: Missing?  Bad links or formatting?
* API changes: These should be very rare but are occasionally either necessary 
(intentional) or accidental.  These must be recorded and added in the 
Programming Guide.
** Note: If the API change is for an Alpha/Experimental/DeveloperApi component, 
please note that as well.

*Make sure to check the object doc!*

  was:
Audit new public Scala APIs added to MLlib in 1.4.  Take note of:
* Protected/public classes or methods.  If access can be more private, then it 
should be.
* Documentation: Missing?  Bad links or formatting?

*Make sure to check the object doc!*


> Audit new public Scala APIs for MLlib 1.4
> -----------------------------------------
>
>                 Key: SPARK-7537
>                 URL: https://issues.apache.org/jira/browse/SPARK-7537
>             Project: Spark
>          Issue Type: Sub-task
>          Components: MLlib
>            Reporter: Joseph K. Bradley
>
> Audit new public Scala APIs added to MLlib in 1.4.  Take note of:
> * Protected/public classes or methods.  If access can be more private, then 
> it should be.
> * Documentation: Missing?  Bad links or formatting?
> * API changes: These should be very rare but are occasionally either 
> necessary (intentional) or accidental.  These must be recorded and added in 
> the Programming Guide.
> ** Note: If the API change is for an Alpha/Experimental/DeveloperApi 
> component, please note that as well.
> *Make sure to check the object doc!*



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

Reply via email to