Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 21 Jul 2000 08:54:25 +0200
From:      Udo Schweigert <ust@cert.siemens.de>
To:        "Jordan K. Hubbard" <jkh@zippy.osd.bsdi.com>
Cc:        Kris Kennaway <kris@FreeBSD.ORG>, Gavin Cameron <gavin@itworks.com.au>, stable@FreeBSD.ORG
Subject:   Re: What does -RC mean? was: Re: Stable broken
Message-ID:  <20000721085425.A4918@alaska.cert.siemens.de>
In-Reply-To: <672.964160377@localhost>; from jkh@zippy.osd.bsdi.com on Thu, Jul 20, 2000 at 11:19:37PM -0700
References:  <20000720093305.A367@alaska.cert.siemens.de> <672.964160377@localhost>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 20, 2000 at 23:19:37 -0700, Jordan K. Hubbard wrote:
> > Anyway: it is a little bit annoying that the -stable branch keeps to be broke
> 
> Yes, it's annoying.  No, it wasn't supposed to happen.  Yes, this is a
> special case.  There is usually always at least one right before a
> major release, and the main criteria is deciding what the risk/reward
> ratio is going to be for gating it in vs leaving people with whatever
> version will ship without the quick "under the wire" merge.  In this
> case, Darren messed up pretty badly here and I'm sure he feels bad
> about it.  We're all human and this kind of thing does happen
> occasionally, especially in open source projects where volunteers are
> usually working a full-time job in addition to their work for the
> project.  Learn from the mistakes made and move on is all we can do at
> this point.
> 
> Even with the breakage, it was a reasonable call given the extremely
> outdated nature of the currently shipping ipfilter code and the fact
> that we've been trying to, erm, _strongly encourage_ Darren to take
> real, hands-on ownership of his software in the FreeBSD CVS tree for
> some time now.  Even if his timing could have been a lot better and
> his CVS procedures more correct, it's still a win if we've now managed
> to convince Darren that his IPFilter software and his personal
> maintenance of it are important enough to FreeBSD that we were willing
> to suffer even this level of pain to incorporate it into 4.1.
> 
> It's certainly my hope that Darren will now maintain IPFilter a little
> more consistently (thus avoiding any need to slip anything in at the
> last moment) and in ways that don't break the tree. :)
> 

Thanks for making that clear (to me). I just not wanted to blame anybody
especially not Darren - ipfilter was just an example. I only was concerned
about the quality of the forthcoming release, which could have been affected
due to insufficient testing time. I always argue to people asking me for
a recommendation which free OS to use, that FreeBSD is superior to others
because of the development model: testing in -current, then MFC. So it 
was a supprise that untested code (means: untested in -current) was 
commited for a release. 

Anyway: I see there were some good reasons for it.

I just saw in another thread that a new RC is now to be tested, which also 
means that the release date will shift a little.

Best regards.

-- 
Udo Schweigert, Siemens AG   | Voice      : +49 89 636 42170
ZT IK 3, Siemens CERT        | Fax        : +49 89 636 41166
D-81730 Muenchen / Germany   | email      : ust@cert.siemens.de
PGP-2/5 fingerprint          | D8 A5 DF 34 EC 87 E8 C6  E2 26 C4 D0 EE 80 36 B2


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?20000721085425.A4918>