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? - Mailing list pgsql-docs

From Magnus Hagander
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
Msg-id 20070221185233.GA21607@svr2.hagander.net
Whole thread Raw
In response to 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?  (bubblboy <bubblboy@gmail.com>)
List pgsql-docs
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

pgsql-docs by date:

Previous
From: bubblboy
Date:
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?
Next
From: Magnus Hagander
Date:
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?