Re: New sequencer release 2.2.8

["J. Lewis Muir via Tech-talk" <tech-talk@aps.anl.gov>]

On 01/06, J. Lewis Muir wrote:
> On 01/06, Johnson, Andrew N. wrote:
> > On 1/6/20 1:24 PM, J. Lewis Muir wrote:
> >> On 12/11, Johnson, Andrew N. via Tech-talk wrote:
> >>> The EPICS core developers don't maintain Known Problems pages of
> >>> Base releases any more, although some sites would prefer that we
> >>> did.
> >> 
> >> Are you saying that that page is not updated?
> > 
> > Yup, there were KnownProblems pages on the site for both 3.15.6 and
> > 3.15.7, neither of which had any problems listed in them, they just
> > contained the default content copied from the base/documentation
> > directory. There were several bugs fixed in 3.15.7 which can be seen
> > at https://launchpad.net/epics-base/3.15/3.15.7 that were never
> > documented on the 3.15.6 Known Problems page.
> > 
> > I just removed the links to them.
> 
> Thanks for the clarification and for removing those pages.  I recently
> checked the 3.15.7 known-problems page and concluded that there were
> no known problems since that's what it said, but now I understand that
> there *are* known problems, they're just not listed there, so I'm glad
> you removed those pages.
> 
> 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

Hi, Andrew!

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.

Thanks!

Lewis