commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claude Warren <>
Subject Re: [All] Using "SemVer"?
Date Mon, 21 Oct 2019 11:58:55 GMT
I think there is a belief in the general using public that Apache follows
SemVer for most Java code.  I think that it would be best if each module
specified if it follows SemVer or not -- just to clear up any confusion on
the part of the user.


On Fri, Oct 18, 2019 at 4:08 PM Stefan Bodewig <> wrote:

> On 2019-10-18, Gilles Sadowski wrote:
> > My point/question was whether we do not already follow it.
> We don't, at least not in all components.
> Quite a few of our components don't have a patch number at all and they
> sometimes create minor releases that would be patch releases if we
> followed SemVer. And sometimes we convince ourselves something that in a
> release that would be a major release it is OK to not change the major
> version number. Both ends of this are true for Compress which I happen
> to know best.
> > What would be the additional burden?
> Having to obey more rules.
> Don't get me wrong. I haven't got any problems with components who want
> to adhere to SemVer.
> It is that I just don't think we need to force all components to do
> so. As little as we don't need to force all components to use Maven or
> need to force all components to use an indentation of four spaces. There
> is no reason to standardize this accross components IMHO.
> Stefan
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

I like: Like Like - The likeliest place on the web

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message