[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse-pmc] Draft deprecation policy
|
Looks good. Jeff's question also came up when I read the policy, hence I
would add that it is indeed allowed to deprecate and announce during the
same release.
Dani
|------------>
| From: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|John Arthorne <John_Arthorne@xxxxxxxxxx> |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| To: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|eclipse-pmc@xxxxxxxxxxx |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Date: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|26.10.2009 14:35 |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------>
| Subject: |
|------------>
>--------------------------------------------------------------------------------------------------------------------------------------------------|
|Re: [eclipse-pmc] Draft deprecation policy |
>--------------------------------------------------------------------------------------------------------------------------------------------------|
>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?
Yes, I think so. I just wanted to distinguish in the example between the
deprecation date and the date we announce intent to remove an API -
otherwise we could just start deleting things today that have been
deprecated for several years already, and nobody would have any advance
notice of the removal.
John
Jeff McAffer
<jeff@xxxxxxxxxxxxxxxxx>
Sent by: To
eclipse-pmc-bounces@xxxxxxxxxxx eclipse-pmc@xxxxxxxxxx
g
cc
10/23/2009 09:09 PM
Subject
Re: [eclipse-pmc]
Please respond to Draft deprecation
eclipse-pmc@xxxxxxxxxxx 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?
Jeff
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).
http://wiki.eclipse.org/Eclipse/API_Central/Deprecation_Policy
John_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
_______________________________________________
eclipse-pmc mailing list
eclipse-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse-pmc
