Received: from golem.fourpalms.org (www.fourpalms.org [64.3.68.148]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1C6cgx42915 for ; Mon, 12 Feb 2001 01:38:43 -0500 (EST) (envelope-from lockhart@alumni.caltech.edu) Received: from alumni.caltech.edu (localhost.localdomain [127.0.0.1]) by golem.fourpalms.org (Postfix) with ESMTP id 68E09FEC2; Mon, 12 Feb 2001 06:46:00 +0000 (UTC) Message-ID: <3A8786A8.EB0BB1B7@alumni.caltech.edu> Date: Mon, 12 Feb 2001 06:46:00 +0000 From: Thomas Lockhart Reply-To: lockhart@fourpalms.org Organization: Yes X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdksmp i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane Cc: Peter Eisentraut , Bruce Momjian , PostgreSQL-documentation Subject: Re: release date References: <6469.981917710@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200102/65 X-Sequence-Number: 320 > > > > Release 7.0 > > > > Release date<title> > > <simpara>2000-10-12</simpara> > > </note> > I kinda like having it in the title, actually, because that way the > table-of-contents will show the release date history all on one page. > I frequently find myself trying to guess which release cycle a given > past date was in --- and AFAIK we have no handy reference anywhere. Hmmph. I'd have guessed that memorizing seven dates would be the least challenging thing you've accomplished in quite some time ;) Anyway, I'll point out that we should try for appropriate markup (whatever that is, but imho probably without dates in chapter titles), and let Peter's upcoming style sheets solve any requirements for output arrangement. Embedding dates in the titles is a short-cut to having a table of release dates, which we should put somewhere in front of the release notes chapters... - Thomas