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 Andrew Hammond
Subject 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 1172020743.099243.7640@l53g2000cwa.googlegroups.com
Whole thread Raw
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
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.

Andrew


pgsql-docs by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [GENERAL] Password issue revisited
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?