public inbox for [email protected]  

help / color / mirror / Atom feed

From: Bruce Momjian <[email protected]>
To: Peter Eisentraut <[email protected]>
Cc: Neil Conway <[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 10:08:33 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>

Peter Eisentraut wrote:
> 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

If they _must_ be done the way you suggest, why have we been able to
generate reliable release notes all these years?

Basically, I think release notes are more efficiently written in batch
mode, meaning all at once --- sure, we could do it incrementally, but it
is more work to fiddle with it in pieces.

I want people to focus on reliable commit messages and I can handle the
release notes part.  The one advantage of incremental is that folks can
see what we have added so far, but it doesn't seem worth the extra work.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  [email protected]               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

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