Message-Id: <470E549D.EE98.0025.0@wicourts.gov>
Date: Thu, 11 Oct 2007 16:51:41 -0500
From: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
To: "Bruce Momjian" <bruce@momjian.us>
Cc: <pgsql-hackers@postgresql.org>
Subject: Re: Release notes introductory text
References: <470E40B2.EE98.0025.0@wicourts.gov>
	<200710112034.l9BKYEA26708@momjian.us>
In-Reply-To: <200710112034.l9BKYEA26708@momjian.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

>>> On Thu, Oct 11, 2007 at  3:34 PM, in message
<200710112034.l9BKYEA26708@momjian.us>, Bruce Momjian <bruce@momjian.us> =
wrote:

> The indent was to say we got a lot done in
> one year.  You have a suggestion?
=20
My suggestion would be to stay away from statements about the speed
of development and focus on the user benefits of the release.
=20
Before my previous post I asked a manager to read the statement and
let me know what he thought, and he said that it "sounds great if it
works" but that it sounded like something was being rushed into
production, which in his experience always meant a lot of bugs.  I
think everyone who contributed to these major improvements deserves
to be proud of their productivity, but it's hard to talk about that
in public without generating the wrong impression.
=20
Come to think of it, a statements about high productivity, valuable
contributions, and community effort all spin OK.  I would stay away
from "heroic effort," though, as it is used in a negative way in
some "agile programming" documents.
=20
Again, above all, focus on answering the question:
=20
"What benefit do I get from moving to this release?"
=20
-Kevin
=20