Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse-pmc] Draft deprecation policy

Looks good John.  Comments/questions:

In the Retention Policy section there is the following:
"In at least two subsequent minor (annual) releases after the release in 
which the intent to remove the deprecated API is announced. For example
if an API is deprecated in release 2.0, and the intent to remove the API is
announced in release 2.1, it will continue to exist in 2.2 and 2.3, but may
be deleted in 2.4 and beyond. "

Is it acceptable to deprecate something and simultaneously announce an intention to remove it?  So then you deprecate and announce in 2.0, it stays in 2.1 and 2.2 but may be gone in 2.3?


On 2009-10-23, at 5:43 PM, John Arthorne wrote:

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).

eclipse-pmc mailing list

Back to the top