Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "WTP Provisional API Reduction"

(Plan)
(Reports)
Line 2: Line 2:
  
 
Indigo report (2670 classes) [[WTP Provisional API Reduction/Indigo|Indigo provisional API]]
 
Indigo report (2670 classes) [[WTP Provisional API Reduction/Indigo|Indigo provisional API]]
 
+
* Finding "provisional" and "experimental"
 +
* Many deprecated classes still marked provisional
 +
* Many "internal" and "provisional" classes.
  
  
Line 8: Line 10:
 
* Team's and adopters inspect reports.  
 
* Team's and adopters inspect reports.  
 
* Gather adopter usage of these api's
 
* Gather adopter usage of these api's
 +
* We don't want to break compatibility  (namespace / package changes)
 
* Team's identify and propose classes that will graduate to API in the short term(Juno M6)
 
* Team's identify and propose classes that will graduate to API in the short term(Juno M6)
 
* Team's propose longer term plan for reduction (post Juno)
 
* Team's propose longer term plan for reduction (post Juno)

Revision as of 14:59, 23 February 2012

Reports

Indigo report (2670 classes) Indigo provisional API

  • Finding "provisional" and "experimental"
  • Many deprecated classes still marked provisional
  • Many "internal" and "provisional" classes.


Plan

  • Team's and adopters inspect reports.
  • Gather adopter usage of these api's
  • We don't want to break compatibility (namespace / package changes)
  • Team's identify and propose classes that will graduate to API in the short term(Juno M6)
  • Team's propose longer term plan for reduction (post Juno)

Back to the top