Hi,
On 23.3.2015 18:07, Peter Geoghegan wrote:
> On Mon, Mar 23, 2015 at 10:01 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>> I'm a little confused as to the status of this patch. It's marked as
>> Waiting on Author in the CommitFest application, and the last patch
>> version was posted in December. The fact that the new CommitFest
>> application encourages people to blindly move things to the next CF
>> instead of forcing patch authors to reopen the record when they update
>> the patch is, IMHO, not good. It's just going to lead to the CF
>> application filling up with things that the authors aren't really
>> working on. We've got enough work to do with the patches that are
>> actually under active development.
>
> Maybe there should be a "stalled" patch status summary, that
> highlights patches that have not had their status change in (say) 2
> weeks. Although it wouldn't really be a status summary, since that
> they're mutually exclusive with each other in the CF app (e.g. a patch
> cannot be both "Waiting on Author" and "Ready for Committer").
Not sure how that's supposed to improve the situation? Also, when you
change the status to 'stalled', it only makes it more difficult to
identify why it was stalled (was it waiting for author or a review?).
What might be done is tracking "time since last patch/review", but I
really don't know how we're going to identify that considering the
problems with identifying which messages are patches.
--
Tomas Vondra http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services