From owner-freebsd-doc Mon Aug 30 15:45:12 1999 Delivered-To: freebsd-doc@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id 9CA00152EA for ; Mon, 30 Aug 1999 15:45:06 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id XAA24288; Mon, 30 Aug 1999 23:37:45 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id UAA53503; Mon, 30 Aug 1999 20:05:13 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Mon, 30 Aug 1999 20:05:13 +0100 From: Nik Clayton To: Jun Kuriyama Cc: iwasaki@jp.FreeBSD.org, doc@freebsd.org Subject: Re: doc/ will not freeze Message-ID: <19990830200512.A50805@kilt.nothing-going-on.org> References: <37C577381F4.4889ORESAMACHAN@cosmo.jah.ne.jp> <199908261744.CAA15930@tasogare.imasy.or.jp> <14280.49435.897747.165T@localhost.sky.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <14280.49435.897747.165T@localhost.sky.rim.or.jp>; from Jun Kuriyama on Sun, Aug 29, 1999 at 02:11:55PM +0900 Organization: FreeBSD Project Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Aug 29, 1999 at 02:11:55PM +0900, Jun Kuriyama wrote: > From: Mitsuru IWASAKI > > BTW, when is the doc code freeze for 3.3-RELEASE? What can we do > > before that? > > Usually, doc tree will not freeze around release because it has no > branch such as RELENG_*. That's true. However, changes to the doc/ tree can interfere with the release building, particularly changes to the make(1) infrastructure. Also, mistaken commits to the content of the documentation can cause the release system to fail as well -- see what happened recently when a new committer forgot to add themselves to the authors.ent file. I think it might be worth having a freeze just to avoid these potential problems. I think the chance of them occuring is small, but it's probably not worth the risk. I'd be interested to hear contrary points of view though. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message