public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Andrew Hammond <[email protected]>
Cc: [email protected]
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
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
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
view thread (32+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
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?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox