Re: Quiet unsure about my question

From: Doug White <dwhite_at_gumbysoft.com>
Date: Tue, 9 Dec 2003 16:33:27 -0800 (PST)
On Tue, 9 Dec 2003, Harald Schmalzbauer wrote:

> I'm tracking -current because I have spare capacity, although it is my
> workstation, and I'm no programmer.
> Now I see, when 5_2 is branched, -current is somewhat different.
> My first question is how do I know that source freeze was annulated?
> Then, what should I (as crash test dummy) track? -current? Isn't it usefull to
> stay with -RC until release happened? You great people solved all my
> (-current) problems even before -beta!

Depends on what you need from a stability standpoint. RELENG_5_2 will
eventually become 5.2-RELEASE, which means that branch is feature-frozen.
Its not likely to change much before the release is cut. Now if you want
to keep up on the latest features and bugfixes, then you could continue to
track -current.

> It's no problem for me to deal with bugs, I just wanted to know if I should
> stay with RC until release!

If you have the resources, running that branch and looking for bugs would
be greatly appreciated. It can only help to improve the release for
everyone.

> Btw: It brings me to one question which was on the TODO list for 5.2: Is the
> ATA RAID1 rebuild panic fixed? Fortunately my drives hadn't died the last 10
> weeks or so, but how do I knwo if I can give it a try? It's no spare machine
> but my private fileserver so availability is not that big problem but
> reliability IS!

The failures were not reproducible on known good hardware. ATA RAID
rebuild is a bit fragile when it comes to flakey hardware, but rebuilds
complete successfully otherwise.  I've tested this 2 or 3 times now
looking at different raid failure scnerios.

-- 
Doug White                    |  FreeBSD: The Power to Serve
dwhite_at_gumbysoft.com          |  www.FreeBSD.org
Received on Tue Dec 09 2003 - 15:33:28 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:33 UTC