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: Magnus Hagander <magnus(at)hagander(dot)net>
- To: Bruce Momjian <bruce(at)momjian(dot)us>
- Cc: Andrew Hammond <andrew(dot)george(dot)hammond(at)gmail(dot)com>, 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: Wed, 21 Feb 2007 09:53:43 +0100
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
- Follow-Ups:
- References:
- Prev 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?
- 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: 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 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: