[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jakarta-general
Subject:    Re: [proposal] Jakarta Deprecation Policy
From:       "Michael McCallum" <michael () spinsoftware ! com>
Date:       2001-05-16 23:07:35
[Download RAW message or body]

> 
> Let us not kid ourselves, a widely distributed API is expected to be backward compatible 
> over *many* major and minor versions. (The distinction between minor and major versions is > 
completely arbitrary.)

The arbitrary nature of the revisions numbers is what gives us the ability to say for the next 
version we deprecate this. 

The changing of the revision numbers represents that the project has evolved into something 
more than it was. And cutting out chaff is a part of the process.

If there is a major number change then the user should expect things to be different thats why 
the developers decided the project needed a major revision number increment.

Making a standard practice just means that the users know how it happens and can pick up any 
jakarta project confidently knowing that the code they write against it will not break (well at least 
in compile time terms ) when the next release is made. 

Michael


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@jakarta.apache.org
For additional commands, e-mail: general-help@jakarta.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]