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?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>
Cc: pgsql-docs(at)postgresql(dot)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?
Date: 2007-02-21 01:22:30
Message-ID: 200702210122.l1L1MUs10246@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-www

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?

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://www.enterprisedb.com

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Magnus Hagander 2007-02-21 08:53:43 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 Message Andrew Hammond 2007-02-21 01:19:03 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?

Browse pgsql-www by date

  From Date Subject
Next Message Robert Treat 2007-02-21 03:10:04 Re: [pgsql-advocacy] Deployment Case Study Presentations
Previous Message Andrew Hammond 2007-02-21 01:19:03 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?