Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Mar 2000 15:32:36 -0600
From:      "Jeffrey J. Mountin" <jeff-ml@mountin.net>
To:        Kris Kennaway <kris@FreeBSD.ORG>, Jamie Norwood <mistwolf@mushhaven.net>
Cc:        Oleg Ogurok <oleg@ogurok.com>, freebsd-stable@FreeBSD.ORG
Subject:   Re: which branch?
Message-ID:  <4.3.2.20000316151715.00b7f4f0@207.227.119.2>
In-Reply-To: <Pine.BSF.4.21.0003161237410.76553-100000@freefall.freebsd. org>
References:  <20000316123220.A90801@mushhaven.net>

next in thread | previous in thread | raw e-mail | index | archive | help
At 12:42 PM 3/16/00 -0800, Kris Kennaway wrote:
>No, I didn't say <3.3 was unstable, I said that we recommend for the
>ultra-conservative folks that they hold off jumping in the pool before
>about then to give the pool-cleaners time to fish out the bugs.

They wait about 6 months.  About 2-4 weeks is sufficient for me.  YMMV

Still have system running 3.0R that is fairly reliable.  Say "fairly" due 
to the vm bug that bites it once in a while.  Knowing what generally causes 
it and how to catch it meant I never got around to updating.  Bad yes, but 
it plays a minor role.  Soon will be 4.0, but hope to be a bit more 
diligent upgrading.

>This is how it's always been in FreeBSD and always will be: except by
>getting the new release "out there" we don't have a hope of being able to
>put it through all of the real-world testing which others can do. If you
>think FreeBSD releases should be made with less bugs and higher quality,
>you need to join the QA program and help find them before it goes out the
>door so they can be fixed before, not after.

Call me adventuresome, but I like to have at least one dot-oh release in 
production.  Gives me time to adjust to new features, etc, etc.

Not to start a big discussion on the release process (again), but for the 
QA team's sake there should be a day or 3 delay between the release tag and 
the grand send off to allow time for 11th hour problems.  The few more 
problematic I saw were fixed.  A minor ones remain, but need to rule out 
hardware/pilot error and none should be show stoppers for anyone.


For those with non-critical needs I heartily recommend 4.0 release or 
stable.  Much, much better than 3.0R's debut.


Jeff Mountin - jeff@mountin.net
Systems/Network Administrator
FreeBSD - the power to serve



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.3.2.20000316151715.00b7f4f0>