Re: CommitFest 2009-09: how do we close this one out?

Lists: pgsql-hackers
From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: CommitFest 2009-09: how do we close this one out?
Date: 2009-10-06 01:34:36
Message-ID: 603c8f070910051834r207ebf64le85e161376043228@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

There are now 19 patches out of an original total of 48 to be dealt
with for this CommitFest. Of those, 10 are marked as "Ready for
Committer", 1 is marked as "Needs Review" and the listed reviewer is a
committer, 7 are waiting for review or re-review by non-committers,
and 1 is waiting on the patch author, as listed below and on
commitfest.postgresql.org. The list below also shows the specific
reviewer/committer, where known.

Because there are so many patches that are ready for committer review
already, and several more that will probably get there soon, it seems
likely that we will still have patches in that state on 10/15, the
nominal date for the end of CommitFest. We need to think about what
we want to do about that. As far as I can see, there are three main
questions that we need to resolve:

1. Do we bundle alpha2 on or shortly after 10/15, or do we wait until
the patches that are ready for committer action have gotten it?

2. Do the committers keep working on the patch queue after 10/15, or
do we postpone patches that are basically ready until 11/15 to give
the committers a break to do their own work? Obviously, postponing
things risks an even longer backlog next time.

Of course, if there's a flurry of activity in the next week these
questions may become moot. But we already have 10 patches marked
"Ready for Committer", which is the highest I can remember seeing, and
there are a couple more that are likely to get to that state soon.

...Robert

Committers (11)
==========
Streaming Replication (Heikki Linnakangas)
Hot Standby (Heikki Linnakangas)
Triggers on columns (Peter Eisentraut)
CREATE LIKE INCLUDING COMMENTS and STORAGE (Andrew Dunstan)
Allow more complex user/database default GUC settings (Alvaro Herrera)
GRANT ON ALL IN schema
Largeobject access controls
Named and mixed notation support
DML node in support of writeable CTEs
Buffer usage in EXPLAIN and pg_stat_statements
Encoding issues in console and eventlog on win32 (Magnus Hagander)

Reviewers (7)
=========
Reworks for Access Controls (Stephen Frost)
Pgbench Shell command (Dan Colish/Gabrielle Roth)
Enhancements to COPY (error logging and autopartitioning) (Selena
Deckelmann/Jeff Davis)
Dynamic cursor support for ECPG (Dan Colish)
SQLDA support for ECPG (Noah Misch)
DESCRIBE [OUTPUT] support for ECPG
Out of scope cursor handling for ECPG

Patch Authors (1)
=============
psql: Unicode UTF-8 table formatting for text output


From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommitFest 2009-09: how do we close this one out?
Date: 2009-10-11 02:55:47
Message-ID: 603c8f070910101955j7f3c3aees558d6d670e057f00@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Mon, Oct 5, 2009 at 9:34 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Because there are so many patches that are ready for committer review
> already, and several more that will probably get there soon, it seems
> likely that we will still have patches in that state on 10/15, the
> nominal date for the end of CommitFest.  We need to think about what
> we want to do about that.

Since the silence in response to this email has been deafening, I
suppose I'll make a concrete proposal.

After some thought and reflection, I'm inclined to suggest that on
10/15 we move all the remaining patches to the next CommitFest,
declare this one closed, and stamp alpha2 on schedule.

If nothing else gets committed between now and then, it will be a
somewhat lighter alpha than what I at least was expecting, but maybe
that's OK. The alternative is to wait, say, another week, and hope
some more things get committed, but they might not, in which case
we've postponed the alpha for nothing.

One bad thing about postponing things to the next CF is that it may
lead to the next CF being really big, but perhaps if some things get
committed after the end of this CommitFest and before 11/15 it won't
be too bad.

The one patch that I would really like to see get some committer
review yet this week is "Reworks for Access Controls", because there
is future work that depends on it.

Thoughts? Votes?

...Robert


From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommitFest 2009-09: how do we close this one out?
Date: 2009-10-11 05:37:29
Message-ID: 7048209E-AC8A-4FCC-98DA-376ADE8AF574@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Oct 10, 2009, at 7:55 PM, Robert Haas wrote:

> After some thought and reflection, I'm inclined to suggest that on
> 10/15 we move all the remaining patches to the next CommitFest,
> declare this one closed, and stamp alpha2 on schedule.

+1, FWIW.

David