| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 2018-03 CF Cleanup |
| Date: | 2018-04-10 18:41:45 |
| Message-ID: | d9fe7d95-dccf-19c0-b025-ab7349a9f840@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2018-04-10 18:58:37 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |
| Previous Message | Alvaro Herrera | 2018-04-10 18:32:47 | Re: pgsql: Support partition pruning at execution time |