Re: Please make sure your patches are on the wiki page - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Please make sure your patches are on the wiki page
Date
Msg-id 3555.1225336370@sss.pgh.pa.us
Whole thread Raw
In response to Re: Please make sure your patches are on the wiki page  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Please make sure your patches are on the wiki page
Re: Please make sure your patches are on the wiki page
List pgsql-hackers
Josh Berkus <josh@agliodbs.com> writes:
>> (2) sorting the pending patches by complexity or subject matter

> Sorting them by complexity would be great, if I thought I could do it.  I'm 
> not sure I can.

We organized them by subject matter (or code area, really) in a couple
of the earlier fests.  I thought that was helpful then.  On the other
hand, the September fest didn't seem to break down that way.  Until we
see the final list it's hard to say how November will shake out.

Earlier today I had a different thought about how to sort things early
in the fest.  I think that there is a strong temptation to finish off
the "simple" patches quickly so as to reduce the size of the list ---
I know I've done that and I think others have too.  The trouble with
simple-first is that problematic patches get left till later, which
means that their authors don't have as much time to respond to any
criticisms that may ultimately be forthcoming.  I think it'd be a good
idea to intentionally try to focus on difficult patches early, so that
they can be bounced back to their authors with useful criticism while
there's still time to do something in response.  Not sure about details
of this, but seems like a process issue that we ought to consider.
        regards, tom lane


pgsql-hackers by date:

Previous
From: KaiGai Kohei
Date:
Subject: Re: Updates of SE-PostgreSQL 8.4devel patches (r1155)
Next
From: Tom Lane
Date:
Subject: Re: minimal update