Re: [HACKERS] Remaining 2017-03 CF entries - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Remaining 2017-03 CF entries
Date
Msg-id CA+TgmoboJxsiW0a1zUEXRrVj-e-thp=XQfLAsfAjhmDk7TXNaA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Remaining 2017-03 CF entries  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Fri, Apr 7, 2017 at 3:30 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2017-04-07 16:28:03 -0300, Alvaro Herrera wrote:
>> Peter Geoghegan wrote:
>> > > - can't move to next fest because it's waiting-on-author, which doesn't
>> > >   allow that.  Doesn't strike me as a useful restriction.
>> >
>> > I agree that that CF app restriction makes little sense.
>>
>> What the restriction means is that if a patch is in waiting-on-author,
>> the proper "close" action is to return-with-feedback.  There is no point
>> in moving the patch to the next commitfest if there is no further patch
>> version.
>
> That's true if the patch has been in that state for a while, but if you
> find some relatively minor issues, and then move it soon after, it seems
> to make sense to keep it open in the next CF.

In an ideal world, we wouldn't do that.  Of course, we do not live in
an ideal world...

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [HACKERS] Remaining 2017-03 CF entries
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] [sqlsmith] Unpinning error in parallel worker