Re: 2018-03 CF Cleanup - Mailing list pgsql-hackers

From David Steele
Subject Re: 2018-03 CF Cleanup
Date
Msg-id d9fe7d95-dccf-19c0-b025-ab7349a9f840@pgmasters.net
Whole thread Raw
In response to Re: 2018-03 CF Cleanup  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: 2018-03 CF Cleanup
List pgsql-hackers
On 4/10/18 11:24 AM, Alvaro Herrera wrote:
> David Steele wrote:
> 
>> For the moment I have left all bugs in the 2018-03 CF.  I can can add
>> them to the "Older Bugs" section of the PG 11 Open Items but I'm not
>> convinced that is the best way to track them.  If they are added to
>> "Older Bugs", does that mean they get closed?  Or should we just add a
>> link to the CF entry in "Older Bugs"?
> 
> OpenItem's "Older Bugs" section is generally a way to ignore items
> forever (ie., they don't represent a true Open Item for this release.)
> I think it's better to move these patches to the next commitfest
> instead.

OK, I did it that way and closed the CF.

Thanks,
-- 
-David
david@pgmasters.net


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: pgsql: Support partition pruning at execution time
Next
From: "Joshua D. Drake"
Date:
Subject: Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS