Downgrading from current to release or stable?

[Erik Trulsson]

On Fri, Nov 21, 2003 at 12:06:54PM -0500, C. Ulrich wrote:
> On Fri, 2003-11-21 at 07:14, Peter Risdon wrote:
> > I just moved from 5.1-current to 5.1 release, and fixed a lot of 
> > problems on a horribly unstable box by doing so. I believe downgrading 
> > to stable is very awkward, but others will be better qualified to 
> > discuss that than I am.
> 
> On a related note, I know that following CURRENT is a game of risk, but
> are current branch releases (such as 5.1-RELEASE) intended to be a bit
> more stable and usable than staying constantly up to date with CURRENT?

Yes, that is the intention.

> 
> In other words, is there a pretty good chance that 5.2-RELEASE won't
> break my (non-production) workstation too horribly when it comes out? Or
> does it carry the same exact risks as following CURRENT?

Before a -RELEASE goes out there will have been a period of code freeze
during which no big, potentially disruptive, changes are allowed.
This means that the code that is in a release will have had at least some
time to stabilize, and has been tested by more people than just the person
who wrote the code.

I would say that there is a fairly good chanse 5.2-RELEASE will be fairly
solid when it comes out.  Maybe not quite as stable as 4.9-RELEASE, but a
good deal safer than the latest code from -CURRENT.


-- 
<Insert your favourite quote here.>
Erik Trulsson
ertr1013 at student.uu.se