commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Tompkins <chtom...@gmail.com>
Subject Re: [release-plugin] Preparing for 1.4.
Date Wed, 22 Aug 2018 13:03:54 GMT
Seems reasonable. Should we go with 2.0?

-Rob

> On Aug 22, 2018, at 6:35 AM, Gilles <gilles@harfang.homelinux.org> wrote:
> 
> On Tue, 21 Aug 2018 22:04:12 -0400, Rob Tompkins wrote:
>> I’m curious to gauge what people think here. My general thought is no
>> breaking BC without a major version change. So, even though this is an
>> internal component, we stick with the rules because we never know who
>> else might be using the component, right?
> 
> What potential BC breaking do you refer to?
> 
> Anyways, if something needs fixing in code used internally and
> the clean fix would require breaking compatibility, why not
> change to a new major version?
> 
> Gilles
> 
>> 
>> -Rob
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
> 


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


Mime
View raw message