X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id C859BD1B4EB for ; Fri, 24 Oct 2003 13:06:43 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 85977-07 for ; Fri, 24 Oct 2003 10:06:16 -0300 (ADT) Received: from mail.gmx.net (mail.gmx.de [213.165.64.20]) by svr1.postgresql.org (Postfix) with SMTP id 027D0D1B532 for ; Fri, 24 Oct 2003 10:06:12 -0300 (ADT) Received: (qmail 32321 invoked by uid 65534); 24 Oct 2003 13:06:14 -0000 Received: from dsl-082-082-165-068.arcor-ip.net (EHLO dsl-082-082-165-068.arcor-ip.net) (82.82.165.68) by mail.gmx.net (mp004) with SMTP; 24 Oct 2003 15:06:14 +0200 X-Authenticated: #495269 Date: Fri, 24 Oct 2003 15:06:13 +0200 (CEST) From: Peter Eisentraut X-X-Sender: peter@peter.localdomain To: Neil Conway Cc: Bruce Momjian , Christopher Kings-Lynne , Tom Lane , PostgreSQL Hackers Subject: Re: 7.4 compatibility question In-Reply-To: <1066804676.371.92.camel@tokyo> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200310/1123 X-Sequence-Number: 45805 Neil Conway writes: > So I think we could make the release notes more useful if we provided a > bit more detail in each entry, and documented changes more extensively. > We could also make better use of SGML, for example by adding s to > the release notes where applicable. I think we also need to *really* > maintain the release notes incrementally during 7.5 development, rather > than having Bruce summarize the CVS logs at the end. IMHO, every patch > that makes a significant change should update the release notes, when > the patch is applied. I've been pushing this agenda for a few releases now, but some people have been, er, boycotting it. I think, too, that release notes *must* be written incrementally at the same time that the feature change is made. This is the only way we can get accurate and complete release notes, and the descriptions could even include some context, some motivations, etc. We have release cycles of 10 months, and there is no way we can make sensible release notes by gathering individual commit messages over that period of time. Heck, ECPG has a full Informix compatibility mode and there is no mention of that anywhere, because there was no commit "Add Informix mode." I suggest we just do it like the documentation: If you don't document it, it doesn't exist. If you don't write a line for the release notes, it doesn't exist either. -- Peter Eisentraut peter_e@gmx.net