commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rodney Waldhoff <>
Subject Re: class-mobility between packages
Date Sat, 06 Dec 2003 15:23:00 GMT
On Fri, 5 Dec 2003, Stephen Colebourne wrote:

> The 'line' is the release. Once code is released we have a duty of backwards
> compatability to it. Thats not to say it will never move, but it can only do
> so by deprecating the original.

I think we should be trying harder than that.

While we may not *need* to always maintain backward compatiablity with
unreleased code, in the sense that we haven't promised it to anyone, we
should strive to maintain compatiablity anyway.  To do otherwise is to
harm our early adopters, and to do that is to harm the project itself.

> Some refactoring occurs because of history - collections was a bundle of
> collections written elsewhere rather than a dedicated, planned re-usable
> component. Collections 3.0 switches from bundle to planned, which does
> involve some deprecation moves. It should be much quiter after collections
> 3.0 (lang was much quiter after 2.0).
> Primitives was a special case in that code existed unreleased for so long
> that it became release-like. Hence care has been taken in how it has been
> moved.
> Stephen

- Rod <>

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message