Experimental Physics and Industrial Control System
|
On 12/12/19 2:41 AM, Ben Franksen via Tech-talk wrote:
I don't like to maintain a "known problems" page either, and I agree
that it is better to provide patch releases more often. On the other
hand, making a new release always involves a certain amount of
administrative overhead. In my case, while some of the process is
automated, there remain a few things I have to do manually: (1)
increasing the release number in the configuration, (2) adding release
notes, (3) adding the new version to the Installation page of the docs,
(4) recording this as a patch, (5) tagging the repo, (6) run the build
and tests to make sure if haven't forgot anything, (7) running the
automation that publishes the new release, (8) send an announcement
email to tech-talk.
I guess creating a new release of EPICS base involves much more work.
Adding an item to the "known problems" page and publishing the docs is a
lot more light-weight and requires less care.
The earliest Known Problems page for Base was the
Bug and Fix Report Release 3.13.0Beta4 from 1996, a time when the Base source code was kept in a private CVS repository at Argonne and your lab needed to sign a license agreement with LANL to get access to it. The tests for the IOC code were in a
separate module and had to be run by hand, which took the best part of a day to do (and if your local user-name wasn't 'mrk' you had some editing to do to run some of them as well). As a result they were not run very often, and it wasn't
that unusual for the tests to find bugs (or missing cvs commits) which then had to be fixed before you could finish making the release. Thus making a release was a major project, and not something that could be done every time someone found and fixed
a bug.
As Ben said, a Known Problems page was a much simpler and quicker way to get fixes out to the other sites, and providing patches was a lot more convenient for users who already had the code installed. EPICS wasn't Open Source, so new users were much less common
and we optimized the process for our existing users, not for newcomers.
- Andrew
--
Complexity comes for free, Simplicity you have to work for.
|
- References:
- New sequencer release 2.2.8 Benjamin Franksen via Tech-talk
- 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 Michael Davidsaver via Tech-talk
- Re: New sequencer release 2.2.8 Ben Franksen via Tech-talk
- Navigate by Date:
- Prev:
Re: New sequencer release 2.2.8 Mark Rivers via Tech-talk
- Next:
RE: Building Epics base 3.15.7 on Windows 7 64bit Freddie Akeroyd - UKRI STFC 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
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: New sequencer release 2.2.8 Mark Rivers via Tech-talk
- Next:
ci-scripts 2.0 release Ralph Lange 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
2021
2022
2023
2024
|
ANJ, 12 Dec 2019 |
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·
·
Search
·
EPICS V4
·
IRMIS
·
Talk
·
Bugs
·
Documents
·
Links
·
Licensing
·
|