Community
Participate
Working Groups
Projects should leverage only published APIs of dependencies. As a Release Review requirement, deviations should be listed as part of a migration plan, with bugs listed where APIs need to be provided by dependent projects.
As per the Jan 7 PC meeting [1], the requirement text was clarified as follows: - All deviations *must* be documented - Rectifications *should* be planned Full new text below: Projects should leverage only published APIs of dependencies. As a Release Review requirement, all deviations must be documented. Additionally, rectification for the issues should be listed as part of a migration plan, with bugs listed where APIs need to be provided by dependent projects. '''Perhaps a '99 44/100% Pure APIs' indicator for projects with no improper usage can be used to advertise the 'cleanest' projects?''' ;) Verification by [http://www.eclipse.org/pde/pde-api-tools/ PDE API Tools] [1] http://wiki.eclipse.org/Planning_Council/Jan_07_2009
THis is a routine mass closing of the previous release umbrella tracking bugs.