Re: 8.4 release planning

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, jd(at)commandprompt(dot)com, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: 8.4 release planning
Date: 2009-01-28 13:59:40
Message-ID: 498064CC.9040500@hagander.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
>> I think the best thing we could do overall is to set release dates and
>> stick to them. If your patch is not ready, well, at least it will get
>> out in a defined amount of time. Right now, the *real* problem with it
>> being pushed to the next release is you don't know how successful some
>> other guy will be at persuading us to delay the next release.
>
> +1, LOL.
>
> Let's not forget that we've already got CTE, window functions, partial
> vacuums, and column-level permissions, all of which are major features
> that should benefit a lot of people. I hope Hot Standby gets
> committed but even if it doesn't, I'm still going to get a lot of
> benefit out of this release, so I'd like it to happen on some sort of
> reasonable time scale.

Agreed. Even without HS, this will be one of the biggest releases we've
had in a while, IMHO.

//Magnus

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2009-01-28 14:02:14 Re: How to get SE-PostgreSQL acceptable
Previous Message Magnus Hagander 2009-01-28 13:57:57 Re: 8.4 release planning