Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
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: Tue, 20 Feb 2007 20:22:30 -0500 (EST)
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. +
- Follow-Ups:
- References:
- Prev by Date: 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 by Date: 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 by thread: 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 by thread: 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?
- Indexes: