Date: Tue, 26 Feb 2002 09:42:26 -0500 From: Michael Lucas <mwlucas@blackhelicopters.org> To: freebsd-doc@FreeBSD.ORG Subject: Official -doc freeze proposal (was Re: docs/35155: [PATCH] Misc corrections to the Handbook, chapter 2) Message-ID: <20020226094226.B55250@blackhelicopters.org> In-Reply-To: <200202221535.g1MFZx236793@bmah.dyndns.org>; from bmah@FreeBSD.ORG on Fri, Feb 22, 2002 at 07:35:59AM -0800 References: <200202202000.g1KK08V36428@freefall.freebsd.org> <20020221115732.GA575@rhadamanth> <20020221170951.B30225@blackhelicopters.org> <20020222.085904.28781226.hrs@eos.ocn.ne.jp> <200202221535.g1MFZx236793@bmah.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Feb 22, 2002 at 07:35:59AM -0800, Bruce A. Mah wrote: > I think your call for a "doc freeze" during the release cycle is a good > idea, and I'd like to see us start doing this. Guys, This is simple enough to do, and discussion seems to have faded. If we want this as policy, it should be in the Release Engineering schedule and the FDP. I propose an official one-week doc/en_US.ISO8859-1 freeze for everything except the release notes, to give translators a little bit of catch-up time. The release notes are difficult, as the -src committers MFC until just a couple days before. I suggest that we have a "best effort" relnotes freeze. Basically, the relnotes maintainer will try to keep things up-to-date so that updates during the last couple days are minimal. Bruce already does this, but it would be important for his successor to be as reliable. ==ml -- Michael Lucas mwlucas@FreeBSD.org, mwlucas@BlackHelicopters.org my FreeBSD column: http://www.oreillynet.com/pub/q/Big_Scary_Daemons http://www.blackhelicopters.org/~mwlucas/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020226094226.B55250>