Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 May 2006 15:57:36 +1000
From:      David Nugent <davidn@datalinktech.com.au>
To:        "J. T. farmer" <jfarmer@goldsword.com>
Cc:        stable@freebsd.org
Subject:   Re: FreeBSD 6.1 Released
Message-ID:  <446423D0.8040509@datalinktech.com.au>
In-Reply-To: <44641D1C.2070106@goldsword.com>
References:  <44600A42.7030600@samsco.org>	<44601F4A.9070802@elischer.org>	<446021DE.6040507@rogers.com>	<20060511210912.GA1344@zaphod.nitro.dk>	<4463DC96.70908@rogers.com>	<446402BB.7050201@alumni.rice.edu> <44640422.1000006@rogers.com> <44641D1C.2070106@goldsword.com>

next in thread | previous in thread | raw e-mail | index | archive | help
J. T. farmer wrote:

> Mike Jakubik wrote:
>
>> Jonathan Noack wrote:
>>
>>> The *entire* errata page was from 6.0; it was a mistake.  This wasn't
>>> some "put on the rose-colored classes and gloss over major issues"
>>> thing.  It was a long release cycle and something was forgotten.  C'est
>>> la vie.  It's always a good idea to check the most up-to-date 
>>> version of
>>> the errata page on the web anyway, so it's *not* too late to update 
>>> it.   
>>
>> How convenient. These problems needed to be addressed in the release 
>> notes, not some on line version.
>
> *Plonk*
>
> You've just entered into my "do not read" bucket.  If you can't see
> that errors occur, then I pity _anyone_ who codes for you...  Or
> perhaps you never make a mistake.  That must be it.


While I tend to agree with regards to poor attitude (see similar threads 
in almost any open source forum on the topic of "demanding" anything 
from a volunteer project), Mike is obviously quite passionate about and 
has the interests of FreeBSD at heart, and for that I cannot blame him 
at all. He seems to have a disagreement with handling of the release 
process, which is the same recurring issue every time there is a release 
and probably the #1 cause of burnout with the Release Engineer of the day.

Historically, you can see that the current process works though, even if 
it may not produce the 100% perfect -RELEASE it at least guards against 
more serious problems that have happened in the past that were 
introduced by last minute and untested changes.


Regards,
David


PS: cc -hackers removed



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