Date: Wed, 21 Feb 2007 19:52:33 +0100
From: Magnus Hagander <magnus@hagander.net>
To: bubblboy <bubblboy@gmail.com>
Cc: Andrew Hammond <andrew.george.hammond@gmail.com>,
	Bruce Momjian <bruce@momjian.us>, pgsql-docs@postgresql.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?
Message-ID: <20070221185233.GA21607@svr2.hagander.net>
References: <20070221085343.GB19713@svr2.hagander.net>
	<200702211430.l1LEUlO00243@momjian.us>
	<20070221144716.GA21044@svr2.hagander.net>
	<5a0a9d6f0702210956g4dd9cc72gcc363ee7b6aa7615@mail.gmail.com>
	<45DC92B4.9060800@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <45DC92B4.9060800@gmail.com>
User-Agent: Mutt/1.5.11

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