Re: Not ready for 8.3

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: "Bruce Momjian" <bruce(at)momjian(dot)us>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>
Subject: Re: Not ready for 8.3
Date: 2007-05-15 15:54:25
Message-ID: 87odkmqdzi.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Bruce Momjian" <bruce(at)momjian(dot)us> writes:

> I think the only other thing we _could_ do is to re-open normal 8.3
> development, so we aren't hampering updates to trivial parts of the
> code. Many of the patches now in the queue had been developed for months
> before 8.3 started, so the hope is that we wouldn't have many more new
> large patches, but several small ones we could deal with while we
> whittle away at the larger patches during the next few months.
>
> The question is whether it is healthy for us to remain in feature freeze
> for months, and if it is unhealthy, what are our options?

I don't see any reason development has to stop while the tree is in feature
freeze. If it led to patches being ready for review and getting reviewed and
committed early in the cycle rather than just before release I think it would
actually be extremely healthy.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Huxton 2007-05-15 16:10:59 Re: Concurrently updating an updatable view
Previous Message Heikki Linnakangas 2007-05-15 15:37:28 Bulk inserts and usage_count