Date: Mon, 30 Aug 1999 20:05:13 +0100 From: Nik Clayton <nik@freebsd.org> To: Jun Kuriyama <kuriyama@sky.rim.or.jp> Cc: iwasaki@jp.FreeBSD.org, doc@freebsd.org Subject: Re: doc/ will not freeze Message-ID: <19990830200512.A50805@kilt.nothing-going-on.org> In-Reply-To: <14280.49435.897747.165T@localhost.sky.rim.or.jp>; from Jun Kuriyama on Sun, Aug 29, 1999 at 02:11:55PM %2B0900 References: <37C577381F4.4889ORESAMACHAN@cosmo.jah.ne.jp> <199908261744.CAA15930@tasogare.imasy.or.jp> <14280.49435.897747.165T@localhost.sky.rim.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 29, 1999 at 02:11:55PM +0900, Jun Kuriyama wrote:
> From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990830200512.A50805>