From owner-freebsd-doc Tue Aug 31 9:48:33 1999 Delivered-To: freebsd-doc@freebsd.org Received: from mail.yk.rim.or.jp (mail.yk.rim.or.jp [202.247.130.37]) by hub.freebsd.org (Postfix) with ESMTP id ED5FE14D56; Tue, 31 Aug 1999 09:48:30 -0700 (PDT) (envelope-from k-horik@yk.rim.or.jp) Received: from localhost (ppp933.yk.rim.or.jp [202.247.185.184]) by mail.yk.rim.or.jp (8.8.8/3.6W-RIMNET-98-06-09) with ESMTP id BAA08225; Wed, 1 Sep 1999 01:48:16 +0900 (JST) To: nik@freebsd.org Cc: kuriyama@sky.rim.or.jp, iwasaki@jp.FreeBSD.org, doc@freebsd.org Subject: Re: doc/ will not freeze From: horikawa@jp.freebsd.org In-Reply-To: Your message of "Mon, 30 Aug 1999 20:05:13 +0100" <19990830200512.A50805@kilt.nothing-going-on.org> References: <19990830200512.A50805@kilt.nothing-going-on.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990901014753F.k-horik@yk.rim.or.jp> Date: Wed, 01 Sep 1999 01:47:53 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 39 Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The Following is my personal opinion. I know mainly about doc/ja_JP.eucJP/man and I know little about handbook and FAQ. (I am a Japanese translator who make diffs to doc/ja_JP.eucJP/man and ask Mr. Kuriyama to apply the diffs) Before RELEASEs were released, some approved commits were made while src/ tree had been frozen. These approved commits sometimes included manual pages updates. Before RELEASE, I want to update translated manual pages when original manual pages is updated while src/ is frozen. This is because it is important to keep original manual pages and translated ones in sync when RELEASE is made. If commits approved by you (and/or nominated persons from each translation team) are allowed, I do not mind doc/ tree freeze before RELEASE. From: Nik Clayton > 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. -- Kazuo Horikawa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message