LISTSERV mailing list manager LISTSERV 16.5

Help for XROOTD-DEV Archives


XROOTD-DEV Archives

XROOTD-DEV Archives


XROOTD-DEV@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XROOTD-DEV Home

XROOTD-DEV Home

XROOTD-DEV  September 2010

XROOTD-DEV September 2010

Subject:

Re: Version Numbers

From:

Brian Bockelman <[log in to unmask]>

Date:

17 Sep 2010 08:21:20 -0500Fri, 17 Sep 2010 08:21:20 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (52 lines)

Hi,

A traditional major.minor.patch sounds good to me.  I do not particularly like the linking recommendations that APR has, which are:

libNAME-MAJOR.so.0.MINOR.PATCH

I would like to avoid tying a particular compilation style with the versioning scheme.

I would propose:
1) MAJOR is incremented for non-backward-compatible wire compatibility, source compatibility, or binary compatibility changes
2) MINOR is incremented for backward-compatible wire, source, or binary compatibility changes.  MINOR changes may not be forward compatible.
3) PATCH is incremented when there are no wire, source, or binary compatibility changes.

So,
- It is safe to upgrade or downgrade within the same MAJOR.MINOR release.
- It is safe to upgrade within the same MAJOR release.
- No guarantees are made between MAJOR releases.

I like version numbers that are informative to the sysadmins like this.  I also think the version numbers should be separate to the release policy and the support policy.

Brian

On Sep 17, 2010, at 2:05 AM, Peter Elmer wrote:

> Hi,
> 
> On Sep 17, 2010, at 8:41, Dirk Duellmann <[log in to unmask]> wrote:
>> since the last call I had a look at several existing project policies and it seems to me that 
>> classical major.minor.patch structure should work well and most users will 
>> have a reasonable expectation what a version change means. For a more formal definition 
>> of the change semantics in each number we could maybe adapt eg the simple approach 
>> described on
>> http://apr.apache.org/versioning.html
> 
> This also seems reasonable to me. (I think the date-time scheme was my
> fault^H^H^H^H^Hidea, and was only really meant for the very early period,
> now years ago, in xrootd development when only a few places deployed it
> and usually were very close to the latest version. A more standard scheme is long
> since due!) 
> 
>                                  Pete
> 
> -------------------------------------------------------------------------
> Peter Elmer     E-mail: [log in to unmask]      Phone: +41 (22) 767-4644
> Address: CERN Division PPE, Bat. 32 2C-14, CH-1211 Geneva 23, Switzerland
> -------------------------------------------------------------------------
>> 




Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use