Re: New sequencer release 2.2.8

["Johnson, Andrew N. via Tech-talk" <tech-talk@aps.anl.gov>]

On 12/11/19 11:01 AM, J. Lewis Muir via Tech-talk wrote:

On 12/11, Benjamin Franksen via Tech-talk wrote:

(I just received the third bug report and the second fix for this
problem. Apparently a lot of people use that platform for development
nowadays and nobody looks at the "known problems" page in the docs...).

Yes, that's because the "known problems" page concept is weird, IMO.
EPICS does it too, and I've complained about that previously.  People
expect that if you know about a problem, you will fix it and make a new
patch release.

The EPICS core developers don't maintain Known Problems pages of Base releases any more, although some sites would prefer that we did. The idea of them was to provide patches that sites could apply to existing installations instead of their having to install a complete new version with an updated version number and then have to reinstall (or at least re-configure and build) everything downstream of Base. Unless you have an automated configure+build system like Sumo the latter can take a lot more effort.

Mark Rivers pointed out that Red Hat do provide a Known Issues page, but I think that's just for the things they know about at release-time; I don't think they update those as new issues are discovered after the release, which is what I used to do for Base.

- Andrew

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