Hi Ben,
On Tuesday 10 February 2009 13:46:23 Benjamin Franksen wrote:
> >
> > Yup, we currently only have branches at the 2nd level number (3.13.x,
> > 3.14,x. trunk), although if we needed to we could create a branch for a
> > 3rd-level we could. By linking patches from the Known Problems page
> > we're making fixes available to people without promising that the result
> > has been tested in the same way that an official release is.
>
> Hm, that sounds as if one should very carefully consider whether to apply
> such patches.
I would agree that a cure is not always better than the illness, depending how
good your doctor is...
> > The EPICS
> > developers at the APS are too busy to do anything more than that, but if
> > someone else wants to help with the release process we could re-think
> > that.
>
> It depends. How much & what kind of work is requested? What, in fact, /is/
> the test procedure you observe for testing an official release?
The full release procedure that I try to follow can be found in the
base/documentation directory, or for R3.14.10 it's here:
http://www.aps.anl.gov/epics/base/R3-14/10-docs/ReleaseChecklist.html
- Andrew
--
The best FOSS code is written to be read by other humans -- Harold Welte
- References:
- Re: Base 3.14.11 Release Timetable Andrew Johnson
- Re: Base 3.14.11 Release Timetable Benjamin Franksen
- Navigate by Date:
- Prev:
Re: Base 3.14.11 Release Timetable Benjamin Franksen
- Next:
libCom tests results 32 bit compatibility mode on windows vista 64 Jeff Hill
- Index:
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: Base 3.14.11 Release Timetable Benjamin Franksen
- Next:
RE: Base 3.14.11 Release Timetable Jeff Hill
- Index:
2002
2003
2004
2005
2006
2007
2008
<2009>
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|