Re: [PROPOSAL] Deprecation policy ( Re: [Proposal] LogKit Release Plan )

[Peter Royal]

On Saturday, February 1, 2003, at 04:26  AM, Nicola Ken Barozzi wrote:

Removing deprecated classes between major versions is a safe bet.
Between point versions it's a possibility.
Between fixes it's an error.

I'd suggest the following as a guideline:

- deprecating classes results in @deprecated being added
- in the next minor point release, they are moved to a
  deprecated source tree for the component that is compiled
  *after* the main ones, so that we are sure that /we/ do not
  rely on those.
- in the major releases the classes can be removed with a vote.

Thoughts?

I'm in agreement on this provided that a major release constitutes X.0 -> Y.0. This would be consistent with Sun's usage of deprecation, where no JDK deprecated classes have been removed since we have only gone from 1.0 -> 1.4.
-pete


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]