I have been using semver for Commons components I am involved. I think we are pretty good in general about it... YMMV ;-)
Gary On Mon, Oct 21, 2019 at 7:59 AM Claude Warren <cla...@xenei.com> wrote: > 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. > > Claude > > On Fri, Oct 18, 2019 at 4:08 PM Stefan Bodewig <bode...@apache.org> 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: dev-unsubscr...@commons.apache.org > > For additional commands, e-mail: dev-h...@commons.apache.org > > > > > > -- > I like: Like Like - The likeliest place on the web > <http://like-like.xenei.com> > LinkedIn: http://www.linkedin.com/in/claudewarren >
