From owner-freebsd-stable@FreeBSD.ORG Wed Mar 18 13:38:15 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 372301065672 for ; Wed, 18 Mar 2009 13:38:15 +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 099678FC21 for ; Wed, 18 Mar 2009 13:38:15 +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 7FD3F46B2D; Wed, 18 Mar 2009 09:38:14 -0400 (EDT) Date: Wed, 18 Mar 2009 13:38:14 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Ken Smith In-Reply-To: <1237380019.30298.3.camel@bauer.cse.buffalo.edu> Message-ID: References: <1237299551.80881.16.camel@bauer.cse.buffalo.edu> <20090318102134.D55869@ns1.as.pvp.se> <1237380019.30298.3.camel@bauer.cse.buffalo.edu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Cc: kama , 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 13:38:17 -0000 On Wed, 18 Mar 2009, Ken Smith wrote: > On Wed, 2009-03-18 at 10:23 +0100, kama wrote: >> Is it possible to get back the todo page during this release phase? > > During the last couple of releases I simply didn't have time to do > everything and this was one of the things that fell by the wayside. > > After the dust from 7.1 settled we started to make arrangements for someone > else to set this up and watch over it for us during the release. It might > take him a little time to get rolling with it (as in it might not appear > immediately upon the release cycle starting) but hopefully we will have > something along these lines come back at some point during this release. While such lists do have downsides ("you shipped even though problem X on your showstopper list wasn't fixed!") they also have some nice advantages -- one is focusing user community testing time and developer community fixing time. At least in the case of 7.2, though, I'm not aware of any major outstanding problems, so focuses for testing are presumably just in the areas of major change from 7.1. Robert N M Watson Computer Laboratory University of Cambridge