Date: Thu, 9 Jan 2003 17:36:49 -0800 From: "David O'Brien" <obrien@FreeBSD.ORG> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: Scott Long <scott_long@btc.adaptec.com>, Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, re-builders@FreeBSD.ORG, bmah@FreeBSD.ORG, re@FreeBSD.ORG Subject: Re: 5.0-RC3 Message-ID: <20030110013649.GA48225@dragon.nuxi.com> In-Reply-To: <20030110012549.GA17013@athlon.pn.xcllnt.net> References: <200301090031.h090V5Ar017298@intruder.bmah.org> <3E1CC4F3.90206@btc.adaptec.com> <3E1DDF76.9010407@btc.adaptec.com> <20030110.095134.71175444.nyan@jp.FreeBSD.org> <3E1E1A7C.2020406@btc.adaptec.com> <20030110012549.GA17013@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 09, 2003 at 05:25:49PM -0800, Marcel Moolenaar wrote: > Let's start the release and have Takahashi-san apply Soren's > patch as an exception. That way it gets some testing and > should increase confidence for a post-RC3 merge. Actually that is the opposite of what should happen -- we need to have Soren's MFC exposed as widely as possible if it is to be in 5.0-R. The way we can get wide[r] coverage is putting it in RC3. Scott, perhaps you can figure out what the MFC would be and apply it and do some sanity testing? > BTW: could we have a policy on the release branch (or HEAD if > that's what we're releasing from) that commits are disallowed > at least 2 hours before the release starts. That way all > changes have been propagated without having to worry about > getting that last commit. Exceptions allowed of course. CVSup from freefall/repoman. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ia64" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030110013649.GA48225>