Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bernd Helmle <mailings(at)oopsware(dot)de>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)
Date: 2009-01-26 11:35:36
Message-ID: 497DA008.6080401@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
> On Sun, 2009-01-25 at 12:06 -0500, Tom Lane wrote:
>
>> Any release with big
> features in it will take longer, whether you wait a year, or not.

Well, big features that land early in the release cycle don't delay the
release. Just the ones that are submitted in the last commit fest.

> I think the choice here is currently between features or release
> schedule, but we could look at things differently and generate some
> other options.

Yeah, that's the tradeoff. features vs. release schedule. I don't see
how else you could look at things.

> What would our users want?

I'm sure it depends on the user. Users that are more interested in the
features we already have in the bag like window functions and
WITH-clause, will obviously prefer to release earlier without hot
standby. And users that want hot standby (or SE-postgresql) will prefer
to delay the release and have those features included.

I don't personally have an opinion, because I don't work with any
real-world databases. It's a tradeoff and both options seem good to me.
I'm going to stick around and keep reviewing Hot Standby as long as it
takes, and when it's ready I can commit it to either 8.4 or 8.5. It's
the same amount of work for me either way.

There's still a list of non-resolved issues that I estimate will take
about two weeks to address. And there's a good possibility that new
issues arise, which require yet more time.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zeugswetter Andreas OSB sIT 2009-01-26 11:48:24 Re: [COMMITTERS] pgsql: Automatic view update rules Bernd Helmle
Previous Message Devrim GÜNDÜZ 2009-01-26 10:44:56 Re: 8.4 release planning (was Re: [COMMITTERS] pgsql: Automatic view update rules)