From owner-freebsd-current Wed Apr 25 0:59:15 2001 Delivered-To: freebsd-current@freebsd.org Received: from ego.mind.net (ego.mind.net [206.99.66.9]) by hub.freebsd.org (Postfix) with ESMTP id EEDE337B422; Wed, 25 Apr 2001 00:59:10 -0700 (PDT) (envelope-from takhus@takhus.mind.net) Received: from takhus.dyn.mind.net (AFN-Dyn-2084622070.pc.ashlandfiber.net [208.46.220.70]) by ego.mind.net (8.9.3/8.9.3) with ESMTP id AAA28648; Wed, 25 Apr 2001 00:59:10 -0700 Received: from localhost (fleisher@localhost) by takhus.dyn.mind.net (8.11.3/8.11.3) with ESMTP id f3P7x9B10894; Wed, 25 Apr 2001 00:59:10 -0700 (PDT) (envelope-from takhus@takhus.mind.net) X-Authentication-Warning: takhus.dyn.mind.net: fleisher owned process doing -bs Date: Wed, 25 Apr 2001 00:59:09 -0700 (PDT) From: Tony Fleisher X-Sender: fleisher@takhus.dyn.mind.net To: "Bruce A. Mah" Cc: freebsd-current@FreeBSD.ORG, freebsd-doc@FreeBSD.ORG Subject: Re: [RFC] RELNOTESng for 5-CURRENT In-Reply-To: <200104241603.f3OG3AB06290@bmah-freebsd-0.cisco.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 24 Apr 2001, Bruce A. Mah wrote: > [...] > > There are two disadvantages to going this route. I think they're > fairly minor: > > 1. Generating a set of release notes requires the DocBook toolchain > to be built, as well as the doc/ subtree. Note that RELNOTESng > will have absolutely no effect on the buildworld/installworld > procedure. > >[...] > > defaulting to off. Once the bugs have been shaken out, I'll make > RELNOTESng the default and stop maintaining the *.TXT files. Eventually, > the *.TXT files will get removed. > Perhaps the *.TXT files could be periodically regenerated to their current location to 1) avoid a POLA violation and 2) allow for at least some RELNOTES without needing DocBook and doc/ (even if they may be slightly out of date). Just an idea.. Tony. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message