| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | 2018-03 CF Cleanup |
| Date: | 2018-04-10 15:17:59 |
| Message-ID: | 5e1628f7-b786-9412-bc2f-fa77c10dea30@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hackers,
I have gone through all the remaining non-bug entries in CF 2018-03 and
pushed them or closed them as appropriate. The majority of the patches
were in Needs Review or Ready for Committer status and I did a brief
review of each to be sure the state was reasonable.
I moved a few Waiting on Author patches where it looked like the patch
was being actively developed even if there was no new patch.
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"?
Thanks,
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2018-04-10 15:24:26 | Re: 2018-03 CF Cleanup |
| Previous Message | Robert Haas | 2018-04-10 15:15:46 | Re: PostgreSQL's handling of fsync() errors is unsafe and risks data loss at least on XFS |