Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020 Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
<== Date ==> <== Thread ==>

Subject: EPICS release series after 7.0: 7.1 or 8.0?
From: "J. Lewis Muir via Tech-talk" <tech-talk@aps.anl.gov>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Date: Tue, 7 Jan 2020 17:01:12 -0600
Hello!

What is the planned EPICS release series after 7.0?  Will it be 7.1 or
8.0?  If it will be 7.1, is the idea that it would be like the 3.11,
3.12, 3.13, 3.14, and 3.15 series where a change in the minor number (in
a <major>.<minor>.<patch> versioning scheme) allows breaking backward
compatibility?

I'm wishing to plan for how I name EPICS packages that I install, and
I want to name them so that they include part of the version in the
package name so that I can install them in parallel (i.e., side by
side).  This is similar to wanting to install both a Python 2 and 3
package and naming them python2 and python3, respectively, so that they
can both be installed at the same time without conflicting with each
other.

To do the same for EPICS, I'm wondering whether I need to include the
major and minor version, or just the major version in the package name.

For example, I could have packages named epics3, epics7, and epics8,
corresponding to 3.15.x, 7.x, and 8.x, but that will only work if the
3.15 series is the last supported series for the 3.x major version,
and the 7.x series are expected to not break backward compatibility
(i.e., 7.x -> 7.[x+1] does not break backward compatibility).

If the series within the 7.x series (i.e., 7.0, 7.1, 7.2, etc.) will be
allowed to break backward compatibility and will likely be supported in
parallel, then I will want to put the major and minor version into the
package name.  For example, epics315, epics70, epics71, etc.

Thank you!

Lewis

Replies:
RE: EPICS release series after 7.0: 7.1 or 8.0? Abdalla Ahmad via Tech-talk
Re: EPICS release series after 7.0: 7.1 or 8.0? Johnson, Andrew N. via Tech-talk

Navigate by Date:
Prev: RE: Ethernet question Mark Rivers via Tech-talk
Next: RE: Ethernet question Mark Rivers via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
Navigate by Thread:
Prev: 回复:回复: Re: help for streamDevice question ws609zyw@163.com via Tech-talk
Next: RE: EPICS release series after 7.0: 7.1 or 8.0? Abdalla Ahmad via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020
ANJ, 08 Jan 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·