[All] Using "SemVer"?

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

[All] Using "SemVer"?

Gilles Sadowski-2
Hello.

In another thread, the question was asked whether "Commons"
follows "SemVer".[1]
It seems to me that we (informally) abide by the intended goal.
Why not state it explicitly (and make it a formal requirement for
a release)?

Regards,
Gilles

[1] https://semver.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Emmanuel Bourg-3
Le 18/10/2019 à 12:46, Gilles Sadowski a écrit :

> Why not state it explicitly (and make it a formal requirement for
> a release)?

-1, it restricts our freedom for no real gain, we have enough
constraints already.

Emmanuel Bourg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Claude Warren
+1 ensures interoperability for our users for minimal pain on our side.

On Fri, Oct 18, 2019 at 12:01 PM Emmanuel Bourg <[hidden email]> wrote:

> Le 18/10/2019 à 12:46, Gilles Sadowski a écrit :
>
> > Why not state it explicitly (and make it a formal requirement for
> > a release)?
>
> -1, it restricts our freedom for no real gain, we have enough
> constraints already.
>
> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Stefan Bodewig
In reply to this post by Gilles Sadowski-2
On 2019-10-18, Gilles Sadowski wrote:

> In another thread, the question was asked whether "Commons"
> follows "SemVer".[1]
> It seems to me that we (informally) abide by the intended goal.
> Why not state it explicitly (and make it a formal requirement for
> a release)?

To me it seems we have often avoided making decisions at a project level
that can be made at a component level.

I'm on the fence here. When a component wants to use SemVer it can say
and do so, but I don't see any reason to enforce such a policy on
components who don't want to follow SemVer.

Stefan

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Gilles Sadowski-2
Hi.

Le ven. 18 oct. 2019 à 14:31, Stefan Bodewig <[hidden email]> a écrit :

>
> On 2019-10-18, Gilles Sadowski wrote:
>
> > In another thread, the question was asked whether "Commons"
> > follows "SemVer".[1]
> > It seems to me that we (informally) abide by the intended goal.
> > Why not state it explicitly (and make it a formal requirement for
> > a release)?
>
> To me it seems we have often avoided making decisions at a project level
> that can be made at a component level.
>
> I'm on the fence here. When a component wants to use SemVer it can say
> and do so, but I don't see any reason to enforce such a policy on
> components who don't want to follow SemVer.

My point/question was whether we do not already follow it.
What would be the additional burden?

Gilles

>
> Stefan
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Stefan Bodewig
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: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

Claude Warren
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 <[hidden email]> 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: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>

--
I like: Like Like - The likeliest place on the web
<http://like-like.xenei.com>
LinkedIn: http://www.linkedin.com/in/claudewarren
Reply | Threaded
Open this post in threaded view
|

Re: [All] Using "SemVer"?

garydgregory
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 <[hidden email]> 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 <[hidden email]> 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: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >
>
> --
> I like: Like Like - The likeliest place on the web
> <http://like-like.xenei.com>
> LinkedIn: http://www.linkedin.com/in/claudewarren
>