On Nov 16, 2011, at 3:02 PM, Doug Cutting wrote:
>
> Another definition is that a major release permits incompatible changes,
> either in APIs, wire-formats, on-disk formats, etc. This is more
> objective measure. For example, one might in release X+1 deprecate
> features of release X but still remain compatible with them, while in
> X+2 we'd remove them. So every major release would make incompatible
> changes, but only of things that had been deprecated two releases ago.
> Often the reason for the incompatible changes is new primary APIs or
> re-implementation of primary components, but those more subjective
> measures would not be the justification for the major version, rather
> any incompatible changes would.
If I wasn't clear, I'd much rather prefer this objective measure.
+1
Arun
|