Experimental Physics and
| |||||||||||||||||
|
On 1/13/20 11:11 AM, J. Lewis Muir wrote:
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.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.8Just 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. HTH, - Andrew -- Complexity comes for free, Simplicity you have to work for.
| ||||||||||||||||
ANJ, 13 Jan 2020 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing · |