From owner-freebsd-stable@FreeBSD.ORG Wed Mar 18 11:38:10 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A98D1106564A for ; Wed, 18 Mar 2009 11:38:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 8493F8FC1A for ; Wed, 18 Mar 2009 11:38:10 +0000 (UTC) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [65.122.17.41]) by cyrus.watson.org (Postfix) with ESMTPS id 3AA3146B2D; Wed, 18 Mar 2009 07:38:10 -0400 (EDT) Date: Wed, 18 Mar 2009 11:38:10 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: kama In-Reply-To: <20090318102134.D55869@ns1.as.pvp.se> Message-ID: References: <1237299551.80881.16.camel@bauer.cse.buffalo.edu> <20090318102134.D55869@ns1.as.pvp.se> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Ken Smith , freebsd-stable Subject: Re: FreeBSD 7.2 Release process starting... X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Mar 2009 11:38:11 -0000 On Wed, 18 Mar 2009, kama wrote: >> Since it's often the case that developers process quite a few outstanding >> MFCs during the last couple days before a code freeze starts I have changed >> RELENG_7 to say it is 7.2-PRERELEASE now as a bit of a heads-up that the >> release cycle is imminent. You might need to be a tiny bit more careful >> using RELENG_7 right now because the odds of you getting a snapshot of the >> tree taken part way through someone doing something that required multiple >> commits goes up during this phase of a release. > > Is it possible to get back the todo page during this release phase? One of the most important things for us to keep an eye on in this release is that the boot loader now works on a number of pieces of hardware on which it reressed for 6.4/7.1. If it proves successful, we'll likely also do errata notes and roll new ISOs for 6.4. Since superpage support was MFC'd, keeping an eye out for new VM problems is important. A number of audit-related changes have been merged improving support for audit pipes, so extra testing of that functionality would be welcome. It would probably be worth skimming svn logs for stable/7 to see what other testing focuses would be particularly useful. Robert N M Watson Computer Laboratory University of Cambridge