Experimental Physics and Industrial Control System

On 06/27/2017 05:53 PM, Benjamin Franksen wrote:
> On 27.06.2017 14:45, Ralph Lange wrote:
>> ...
>> Any opinions on that plan?
>
> (+1) Sound pretty much like a no-brainer to me.

"no-brainer" as in obvious, or "no-brainer" as in this discussion has
turned my brain to mush which is now dribbling out of my ears?

(I've sat through several V4 group meetings on version numerology.)

On 06/27/2017 06:01 PM, J. Lewis Muir wrote:
> ...
> Just curious, in your proposal, you said, "After a release has been
> published, the release number is stepped up...."  What would it be
> stepped up to?  I assume you're talking about within a release series,
> right?  So, for example, for the 3.16 release series, if you just
> published 3.16.1, you would immediately step the version to 3.16.2-DEV?

This should be the smallest possible increment.  In this case
3.16.1.1-DEV with the current 4 part numbers.


or, and I hesitate to suggest anything, include the -DEV flag as the
least significant bit in EPICS_VERSION_INT.

> #define EPICS_VERSION_INT VERSION_INT($ver, $rev, $mod, ($patch)<<1|($isdev))

where $isdev is true if $snapshot is not an empty string.

Attachment: signature.asc
Description: OpenPGP digital signature

Replies:

Re: EPICS Base dev release numbering Ralph Lange

References:

EPICS Base dev release numbering Ralph Lange

Re: EPICS Base dev release numbering J. Lewis Muir

Navigate by Date:

Prev: Re: EPICS Base dev release numbering J. Lewis Muir

Next: Re: EPICS Base dev release numbering Konrad, Martin

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: EPICS Base dev release numbering J. Lewis Muir

Next: Re: EPICS Base dev release numbering Ralph Lange

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024