public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: bubblboy <[email protected]>
Cc: Andrew Hammond <[email protected]>
Cc: Bruce Momjian <[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 19:52:33 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
On Wed, Feb 21, 2007 at 07:43:00PM +0100, bubblboy wrote:
> There is one thing I don't understand in this whole discussion; this
> upgrading, it is not specific to PostgreSQL, is it? Is there not a page
> somewhere on the web that already extensively discusses this issue, no
> matter what the program is? "You should always upgrade because blah
> blah", I ca not imagine nobody wrote such an article yet. And if not;
> write one yourself :) Maybe linking to that article from the postgresql
> documentation, if the need is felt...
What we want to push is that we don't add stuff in stable branches.
Unlike Certain Other Databases that we are often compared to...
//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], [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