| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: a few thoughts on the schedule |
| Date: | 2015-05-13 16:27:14 |
| Message-ID: | 22718.1431534434@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2015-05-13 11:52:40 -0400, Tom Lane wrote:
>> One thing that continues to bother me about the commitfest process is that
>> it's created a default expectation that things get committed eventually.
> Agreed that this is a problem. I think we need to work on giving that
> feedback rather sooner than later. It's one thing to be given a -1 a
> week or two after a patch gets proposed, another being given it 10
> revisions and half a year later.
> How about we really try to triage the patches a) before the CF starts,
> b) half into the CF?
We keep talking about doing something like that (I remember it's come up
several times in the annual developer meetings), and then not actually
doing it. But I agree it seems like a good idea.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Petr Jelinek | 2015-05-13 16:32:53 | Re: Triaging the remaining open commitfest items |
| Previous Message | Tom Lane | 2015-05-13 16:22:41 | Re: Default Roles (was: Additional role attributes) |