EPICS Home EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

Format page
for printing


Search Tech-talk
2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  <2017>  2018  2019  2020  2021  2022  2023  2024 
<== Date ==> <== Thread ==>
Subject: Re: EPICS Base dev release numbering
From: Ralph Lange <[email protected]>
To: EPICS Core Talk <[email protected]>
Date: Tue, 27 Jun 2017 22:25:21 +0200
Hi Lewis,

Yes, exactly.

I would like to keep this as regular as possible.
The stepped-up number should be the next *planned* release on the branch that the development is aimed at, so - using current EPICS Base as an example we are all familiar with - on the release/3.15 branch after releasing 3.15.5, the name would be 3.15.6-DEV, and on the release/3.16 branch after 3.16.1, the name would be 3.16.2-DEV. On master, the name would be 3.17-DEV until the release/3.17 branch is created. At that point the name changes to 3.17.0-DEV on the newly created branch and to 3.18-DEV on master.
This ensures that a name is always unambiguously pointing to one specific segment (between two release tags or branch points) on one specific branch.

The name that Michael proposes (3.16.1.1-DEV) would be used on a release/3.16.1 branch that might be created off the 3.16.1 release tag to prepare an important patch that must be published immediately and cannot wait until the 3.16.2 release.

I think this scheme is clear and easy enough, and it matches and works exactly the same with the Maven project versions on the Java side of things.

Cheers,
~Ralph


On Tue, Jun 27, 2017 at 6:01 PM, J. Lewis Muir <[email protected]> wrote:
On 06/27, Ralph Lange wrote:
> Proposal:
> After a release has been published, the release number is stepped up, then
> "-DEV" is added to the *new* release number to signal a development state.
> The number in front of "-DEV" is the target of development.

[snip]

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?


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 Ralph Lange
Next: RE: Java PvaClientMonitor questions Mark Rivers
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 Ralph Lange
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 
ANJ, 21 Dec 2017 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·