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  <20102011  2012  2013  2014  2015  2016  2017  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
<== Date ==> <== Thread ==>

Subject: Re: epics debian repository update
From: "J. Lewis Muir" <jlmuir@anl.gov>
To: EPICS Tech-Talk <tech-talk@aps.anl.gov>
Date: Thu, 20 May 2010 11:55:28 -0500
On 5/20/10 11:14 AM, Pete R. Jemian wrote:
> Lewis:
> 
> On 5/20/2010 10:44 AM, J. Lewis Muir wrote:
>> I only see six possible combinations:
>>
>> 1. synApps 5.4 + EPICS Base 3.14.10
>> 2. synApps 5.4 + EPICS Base 3.14.11
>> 3. synApps 5.5 + EPICS Base 3.14.10
>> 4. synApps 5.5 + EPICS Base 3.14.11
>> 5. synApps 5.6 + EPICS Base 3.14.10
>> 6. synApps 5.6 + EPICS Base 3.14.11
> 
> There is no synApps 5.6 release yet.  5.5 was released April 21 and is
> compatible with EPICS base 3.14.11 (using it with 3.14.10 or earlier is
> not identified as successful).  synApps 5.4 is not compatible with EPICS
> base 3.14.11, thus some of the options above are not really possible.
> Your next table shows the realistic situation.

Hi, Pete.

Right, I understand that.  David posed it as a hypothetical; I was just
answering within the example he gave.

> We don't release synApps with every bug fix for the proliferation reason
> you cite, as well as that the release process takes some weeks.  Thus,
> we do not do it regularly.  Once we assess that the patch list is
> overwhelming and/or the constituent modules or base have undergone
> significant revision, then a new synApps release is made.

I think this is where things break down.

I can certainly understand not maintaining more than, say, the two most
recent releases of synApps.  Each release you maintain takes time and
you have to limit that.  OpenBSD and various Linux distros work the same
way.  OpenBSD releases every six months and supports the previous
release for six months, thus each release is supported for one year.

But if each module in synApps would actually make bug fix releases that
do not change the API then you could easily include them in synApps and
make bug fix synApps releases.  I don't understand why the release
process takes weeks.  Assuming your release process is automated, I
would think it would take no more than 30 minutes to make a new release
and push it to the web site.  I must be missing something.

Lewis

References:
epics debian repository update Davidsaver, Michael
Re: epics debian repository update J. Lewis Muir
RE: epics debian repository update Davidsaver, Michael
Re: epics debian repository update J. Lewis Muir
Re: epics debian repository update Michael Davidsaver
Re: epics debian repository update J. Lewis Muir
Re: epics debian repository update Pete R. Jemian

Navigate by Date:
Prev: Re: epics debian repository update Pete R. Jemian
Next: Re: epics debian repository update Benjamin Franksen
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
Navigate by Thread:
Prev: Re: epics debian repository update Pete R. Jemian
Next: areaDetectorR1-6.tar Patrick Thomas
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  <20102011  2012  2013  2014  2015  2016  2017 
ANJ, 02 Sep 2010 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·