From owner-freebsd-doc@FreeBSD.ORG Tue Jun 1 17:11:32 2004 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EA12C16A4CE for ; Tue, 1 Jun 2004 17:11:32 -0700 (PDT) Received: from smtp.eos.ocn.ne.jp (eos.ocn.ne.jp [211.6.83.117]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BBA043D49 for ; Tue, 1 Jun 2004 17:11:32 -0700 (PDT) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p44247-adsao12honb4-acca.tokyo.ocn.ne.jp [219.114.51.247]) by smtp.eos.ocn.ne.jp (Postfix) with ESMTP id 8464A1F2B; Wed, 2 Jun 2004 09:11:31 +0900 (JST) Received: from localhost (alph.allbsd.org [192.168.0.10]) by delta.allbsd.org (8.12.9p2/8.12.9) with ESMTP id i520AgA2030980; Wed, 2 Jun 2004 09:10:43 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 02 Jun 2004 09:10:18 +0900 (JST) Message-Id: <20040602.091018.78743978.hrs@eos.ocn.ne.jp> To: pepper@reppep.com From: Hiroki Sato In-Reply-To: References: X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 4.0.64 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Jun__2_09_10_18_2004_053)--" Content-Transfer-Encoding: 7bit cc: freebsd-doc@FreeBSD.org Subject: Re: http://www.freebsd.org/releases/4.10R/relnotes-i386.html questions X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2004 00:11:33 -0000 ----Security_Multipart(Wed_Jun__2_09_10_18_2004_053)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Chris Pepper wrote in : pepper> Is this worth updating, for people like me who read the pepper> release notes on the main website (and haven't upgraded already), or pepper> not really, under the theory that people won't see updated release pepper> notes? I don't see anything that needs to go into errata, which takes pepper> updates post-release... Ah, sorry, almost all of them you pointed out seem my fault... Regardless of whether people will read or not, the release notes should not be updated after the release. This is the same reason why the release distribution itself is not updated due to the errors/bugfixes without bumping the version number. If needed, information on the error should be put into the errata document. Anyway, I appreciate your patch to fix them, especially for English nits---I am not a native speaker and want to learn from it. pepper> /usr/src/release/doc/en_US.ISO8859-1/relnotes/common/new.sgml doesn't pepper> contain the content in the HTML. Is it immediately cleared out after pepper> each release for the next release (4.11R in this case)? If so, that pepper> seems to imply that release notes for a release are never updated pepper> once the release is announced. Am I understanding correctly, or are pepper> 4.10R notes only available from a specific tag, or am I completely pepper> off in the weeds? The release notes for 4.10R is on RELENG_4_10, not RELENG_4. pepper> On a forward-looking note, I notice that references like pepper> ports/UPDATING are not links -- is there any reason they shouldn't be? No. There has been no procedure to add references like ports/UPDATING yet because they are relatively new. I think I will consider them in the next release cycle. -- | Hiroki SATO ----Security_Multipart(Wed_Jun__2_09_10_18_2004_053)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQBAvRrqTyzT2CeTzy0RAqfHAKDdYN9TbiD9R3P9LdJaGppiaVLVFwCfU2He 3vbfmoOkjcjShTRJRmtFKJI= =W04i -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Jun__2_09_10_18_2004_053)----