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? - Mailing list pgsql-docs

From Magnus Hagander
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?
Date
Msg-id 20070221085343.GB19713@svr2.hagander.net
Whole thread Raw
In response to 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?  (Bruce Momjian <bruce@momjian.us>)
Responses 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?  (Bruce Momjian <bruce@momjian.us>)
List pgsql-docs
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

pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
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?
Next
From: Bruce Momjian
Date:
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?