From: Bruce Momjian <bruce@momjian.us>
Message-Id: <200702211430.l1LEUlO00243@momjian.us>
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?
In-Reply-To: <20070221085343.GB19713@svr2.hagander.net>
To: Magnus Hagander <magnus@hagander.net>
Date: Wed, 21 Feb 2007 09:30:47 -0500 (EST)
CC: Andrew Hammond <andrew.george.hammond@gmail.com>,
 pgsql-docs@postgresql.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"

Magnus Hagander wrote:
> 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.

If you look at the developer documentation, you will see I overhauled
the instructions for upgrading a minor release:

	http://momjian.us/main/writings/pgsql/sgml/install-upgrading.html

I think that would be a good place to add more text.  What additional
text do we need?  Something about how you are less likely to hit a new
bug if you minor upgrade than if you stay on an older release?

-- 
  Bruce Momjian  <bruce@momjian.us>          http://momjian.us
  EnterpriseDB                               http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +