Difference between revisions of "WTP Provisional API Reduction"

From Eclipsepedia

Jump to: navigation, search
(Plan)
 
(4 intermediate revisions by one user not shown)
Line 3: Line 3:
 
* Indigo report (2670 classes) [[WTP Provisional API Reduction/Indigo|Indigo provisional API]]
 
* Indigo report (2670 classes) [[WTP Provisional API Reduction/Indigo|Indigo provisional API]]
 
* Juno M5 report (2617 classes) [[WTP Provisional API Reduction/Juno M5|Juno M5 provisional API]]
 
* Juno M5 report (2617 classes) [[WTP Provisional API Reduction/Juno M5|Juno M5 provisional API]]
** Finding "provisional" and "experimental"
+
** Report searched for "provisional" and "experimental" in source comments / removed references to other "provisional" classes
 
** Many deprecated classes still marked provisional
 
** Many deprecated classes still marked provisional
 
** Many "internal" and "provisional" classes.
 
** Many "internal" and "provisional" classes.
Line 15: Line 15:
 
*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)
 +
*Always use [http://wiki.eclipse.org/New_Help_for_Old_Friends_VIII New Help for Old Friends(Kepler)] to report any incompatible changes
 +
 +
=== Parent bug ===
 +
[https://bugs.eclipse.org/bugs/showdependencytree.cgi?id=372410&hide_resolved=1 Provisional API bugs]
  
 
[[Category:Eclipse_Web_Tools_Platform_Project]]
 
[[Category:Eclipse_Web_Tools_Platform_Project]]

Latest revision as of 11:28, 27 November 2012

[edit] Reports

  • Indigo report (2670 classes) Indigo provisional API
  • Juno M5 report (2617 classes) Juno M5 provisional API
    • Report searched for "provisional" and "experimental" in source comments / removed references to other "provisional" classes
    • Many deprecated classes still marked provisional
    • Many "internal" and "provisional" classes.


[edit] 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)
  • Always use New Help for Old Friends(Kepler) to report any incompatible changes

[edit] Parent bug

Provisional API bugs