Date: Thu, 09 Jan 2003 21:20:44 -0700 From: Scott Long <scott_long@btc.adaptec.com> To: Marcel Moolenaar <marcel@xcllnt.net> Cc: "David O'Brien" <obrien@freebsd.org>, Takahashi Yoshihiro <nyan@jp.FreeBSD.org>, re-builders@freebsd.org, bmah@freebsd.org, re@freebsd.org Subject: Re: 5.0-RC3 Message-ID: <3E1E4A1C.9080505@btc.adaptec.com> In-Reply-To: <200301090031.h090V5Ar017298@intruder.bmah.org> 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> <20030110013649.GA48225@dragon.nuxi.com> <20030110014820.GB17013@athlon.pn.xcllnt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Marcel Moolenaar wrote: > On Thu, Jan 09, 2003 at 05:36:49PM -0800, David O'Brien wrote: > > >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. > > > I don't know what the change is, but if it has possible impact on > non-pc98, then yes. > > > >>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. > > > It's better to stop rushing things in... I like at least 5 hours > so that I can run a buildworld first, prepare the box and optionally > start a release early (which I will abort) to flush out commandline > screwups and have enough time to fix last minute bogons... > Formalizing a wait period is probably a very good idea. For now, lets say that Soeren's ata MFC will signal the closing of that branch, and you can start a build any time after that once you are ready. I'll send an email with the signal. We've had some very good bug fixes through the RC period, so slipping a little more to get it right doesn't bother me too much =-) Scott 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?3E1E4A1C.9080505>