On 3/12/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
Dave Page wrote:
> Magnus Hagander wrote:
>> I'm bouncing this over to -www as well to hear what people think about
>> that part. If we do that, I'd definitely like to see a proper page and
>> not just a FAQ link.
>
> Agreed, though there's n
On 2/22/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
>> > On the front page, we already have "Latest Releases" with links to the
>> > most recent release for each version still actively maintained and
>> > release notes. (Would it make sense to change that title from "Latest
>> > Releases" to
On 2/22/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
Andrew Hammond wrote:
> On 2/21/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
>
>> OK, the FAQ now has:
>>
>> The PostgreSQL team makes only bug fixes in minor releases,
>> so, for examp
On 2/21/07, Joshua D. Drake <[EMAIL PROTECTED]> wrote:
All users should upgrade to the most recent minor release as soon
as is reasonable for the environment. While upgrades always have some
risk, PostgreSQL minor releases fix only bugs to reduce the risk of
upgrading. To reduce issues a user ma
On 2/21/07, Bruce Momjian <[EMAIL PROTECTED]> wrote:
OK, the FAQ now has:
The PostgreSQL team makes only bug fixes in minor releases,
so, for example, upgrading from 7.4.8 to 7.4.9 does not require
a dump and restore; merely stop the database server, install
the updated binarie
On 2/21/07, Magnus Hagander <[EMAIL PROTECTED]> wrote:
> > > 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
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
