Skip site navigation (1) Skip section navigation (2)

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?

From: "Andrew Hammond" <andrew(dot)george(dot)hammond(at)gmail(dot)com>
To: pgsql-docs(at)postgresql(dot)org
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: 2007-02-21 01:19:03
Message-ID: 1172020743.099243.7640@l53g2000cwa.googlegroups.com (view raw or flat)
Thread:
Lists: pgsql-docspgsql-www
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


Responses

pgsql-docs by date

Next:From: Bruce MomjianDate: 2007-02-21 01:22:30
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?
Previous:From: Dave PageDate: 2007-02-20 19:47:06
Subject: Re: Password issue revisited

pgsql-www by date

Next:From: Bruce MomjianDate: 2007-02-21 01:22:30
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?
Previous:From: Robert TreatDate: 2007-02-20 06:11:35
Subject: Re: "here" links

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group