Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be 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"

(Reports)
Line 8: Line 8:
  
  
=== Plan ===
+
=== 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)
+
  
 +
*Team's and adopters will 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)
  
 
+
[[Category:Eclipse_Web_Tools_Platform_Project]]
 
+
[[Category:Eclipse Web Tools Platform Project]]
+

Revision as of 15:43, 23 February 2012

Reports

  • Indigo report (2670 classes) Indigo provisional API
  • Juno M5 report (2617 classes) Juno M5 provisional API
    • Finding "provisional" and "experimental"
    • Many deprecated classes still marked provisional
    • Many "internal" and "provisional" classes.


Plan

  • Team's and adopters will 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