public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Neil Conway <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: Christopher Kings-Lynne <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: 7.4 compatibility question
Date: Fri, 24 Oct 2003 15:06:13 +0200 (CEST)
Message-ID: <[email protected]> (raw)
In-Reply-To: <1066804676.371.92.camel@tokyo>

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 <xref>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   [email protected]

view thread (60+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: 7.4 compatibility question
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox