Date: Wed, 21 Feb 2007 09:53:43 +0100
From: Magnus Hagander <magnus@hagander.net>
To: Bruce Momjian <bruce@momjian.us>
Cc: Andrew Hammond <andrew.george.hammond@gmail.com>,
 pgsql-docs@postgresql.org
Subject: Re: should we have a separate page that clearly defines what a minor
	release is and why it's a good idea to keep up with them?
Message-ID: <20070221085343.GB19713@svr2.hagander.net>
References: <1172020743.099243.7640@l53g2000cwa.googlegroups.com>
	<200702210122.l1L1MUs10246@momjian.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200702210122.l1L1MUs10246@momjian.us>
User-Agent: Mutt/1.5.11

On Tue, Feb 20, 2007 at 08:22:30PM -0500, Bruce Momjian wrote:
> Andrew Hammond wrote:
> > I know it's mentioned in the FAQ, but I'd like to have a separate page
> > that describes what a minor release is, and why it's a good idea to
> > keep up with them. Basically, I want something simple and clear to
> > point middle-managers at when they ask me why I want to upgrade the
> > database.
> > 
> > I'm willing to write it, if there's a consensus that it would be worth
> > having.
> 
> I think adding to the FAQ is the best solution.  What additional
> information to we need there?

I think it's important enough (and unclear enough to a lot of people)
that it shuold have it's own non-FAQ section. Either as a page on the
website or as a page in the documentation.

//Magnus