From owner-freebsd-doc Wed Nov 10 15: 1:41 1999 Delivered-To: freebsd-doc@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 33A3A14E23; Wed, 10 Nov 1999 15:01:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 28BC21CD621; Wed, 10 Nov 1999 15:01:39 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 10 Nov 1999 15:01:39 -0800 (PST) From: Kris Kennaway To: Nik Clayton Cc: doc@freebsd.org Subject: Re: Outdated version information In-Reply-To: <19991110080153.A90762@kilt.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 10 Nov 1999, Nik Clayton wrote: > > > I'll be writing this up more fully later, but in a nutshell, the plan is to > modify DocBook to add three new attributes to each element, osversionmin, > osversionmax, osversionequal. This might be useful for other reasons, but it doesn't seem to address the case of lots of instances of things like: "The current version of FreeBSD is 3.2" "the next release coming up with 3.3 in Q3 1999" "For the current 3.0-stable release, 3.0-RELEASE, see the 3.0-RELEASE directory" "...as it continues on its way towards 3.2-RELEASE". "somebody should check this before 3.0 goes out of beta or there'll be a lot of red faces after the CDs ship." just to note a few from a brief scan of the first few pages of the FAQ. The point is that there needs to be some way of flagging these kinds of changes for human revision, not just conditionally including text based on current revision number. Kris ---- Cthulhu for President! For when you're tired of choosing the _lesser_ of two evils.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message