[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [eclipse-pmc] Draft deprecation policy
|
Hi John,
this looks very good! Things that I
noticed:
-
In the section about major releases: "For example if an API is deprecated in release 3.9" you may want to better pick "3.6" as example
for clarity.
-
I do not understand the section "In addition, the Eclipse Project will not delete
deprecated API as part of an Eclipse Foundation simultaneous release..." If this is an
additional constraint, it means that at the point where project X has been
"unable to cease using deprecated API" that API had been announced for removal
for 2 years already! Now if an Eclipse Foundation Release Train project is
unable to cease using API that's scheduled for deletion, that is a bad sign of
the state of that project, isn't it? Should such a project be allowed to
remain on the release train?
Having that statement in there seems to be
unnecessarily weakening our position on API deprecation and deletion. We
should not make the rules softer forrelease train projects, but we should be
making them harder!
-
The section about "Announcing API
Removal" does not specify any technique for how the "to be deleted" status of
API would be processable by automated tools. This may not be necessary in the
context of this policy though. I remember having controversial discussions
about how to do the markup, and the question of markup should not be holding
up the policy. But we may want to add markup information in an addendum at a
later point in time.
-
A corollary of your policy is that at
any point X in time, the current snapshot of the porting guide in CVS has the
exact list of API to be removed from the Eclipse project as well as the times
when removal is scheduled to occur. It may be worth explicitly noting
this.
Thanks for taking action on
this policy!
Martin
PMC members, We've been discussing an Eclipse project deprecation
policy on and off for the past year or so. With some guidance from McQ, I have
written up a draft guideline for further discussion. Please look it over and we
can discuss it at the next PMC call (or feel free to edit/add comments directly
in the wiki page). http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy
John