EPICS Controls 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  <20202021  2022  2023  2024  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  <20202021  2022  2023  2024 
<== Date ==> <== Thread ==>

Subject: Re: New sequencer release 2.2.8
From: "Johnson, Andrew N. via Tech-talk" <[email protected]>
To: "J. Lewis Muir" <[email protected]>
Cc: "[email protected]" <[email protected]>
Date: Mon, 13 Jan 2020 18:20:00 +0000
Hi Lewis,

On 1/13/20 11:11 AM, J. Lewis Muir wrote:
So, what's the best way now to get the latest stable version of an
EPICS release?  In other words, when the known-problems page was being
updated, I would take the latest release and apply all the patches
listed on the known-problems page.  Is there a way to get close to that
now?

A few guesses are:

a. Clone the 3.15 branch of the EPICS repo [1].  That branch is always
   stable.

b. Look through the commits to the 3.15 branch of the EPICS repo [1]
   for anything that looks like a relevant bug fix and apply patches
   corresponding to those commits.  I think this is closest to Michael
   Davidsaver's suggestion.

c. View the milestone that will become the next release (e.g., 3.15.8
   [2] for the 3.15 series), and watch for any targeted bugs with status
   "Fix Committed".  Find the commits that fix the bug, and apply the
   corresponding patches.

Thanks!

Lewis

[1]: https://code.launchpad.net/~epics-core/epics-base/+git/epics-base/+ref/3.15
[2]: https://launchpad.net/epics-base/+milestone/3.15.8
Just following up; have you had a chance to consider this question?

I'm also thinking a fourth option could be:

d. Don't try to get close to the known-problems page of old.  Just use
   the latest stable release.  If you run into a problem, check the bug
   reports for the next milestone in the series and commits for the next
   release to see if the problem has already been fixed and apply an
   appropriate patch if so.
I believe your new option (d) is closest to what other members of the core group have advocated. If there is a specific bug that is fixed on a release series branch that you're using you can also ask us to make a bug-fix release from that series which includes that fix.

HTH,

- Andrew
-- 
Complexity comes for free, Simplicity you have to work for.

References:
Re: New sequencer release 2.2.8 J. Lewis Muir via Tech-talk
Re: New sequencer release 2.2.8 Johnson, Andrew N. via Tech-talk
Re: New sequencer release 2.2.8 J. Lewis Muir via Tech-talk
Re: New sequencer release 2.2.8 J. Lewis Muir via Tech-talk

Navigate by Date:
Prev: pyepics and python3.8; Was: Can't import PyEpics on CentOS 7 Torsten Bögershausen via Tech-talk
Next: Re: pyepics and python3.8; Was: Can't import PyEpics on CentOS 7 Matt Newville 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  <20202021  2022  2023  2024 
Navigate by Thread:
Prev: Re: New sequencer release 2.2.8 J. Lewis Muir via Tech-talk
Next: EPICS R3.15 and menuScan.dbd Michael Westfall 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  <20202021  2022  2023  2024 
ANJ, 13 Jan 2020 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·