Re: [PROPOSAL] Major versions require package name change

[Rahul Akolkar <ra...@gmail.com>]

On 10/29/06, Stephen Colebourne <sc...@btopenworld.com> wrote:
<snip/>
>
> This proposal is about making upgrades *predicatable* at the expense of
> a small amount of pain. I know that most of us don't really like it, but
> I contend that there is no alternative other than to inflict pain on
> users of commons over the next few years, and perhaps risk commons
> becoming irrelevant by being unusable. I also strongly believe we need a
> cross-commons approach on this.
>
<snap/>

Predictable, cross-commons, whats not to like.

I don't know if we risk being unusable, but we may risk being obsolete
first if we keep dragging our baggage. When sweeping changes are
expected out of components, its a good time to go all out.

-Rahul


> Stephen
>

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