From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | David Steele <david(at)pgmasters(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: 2018-03 CF Cleanup |
Date: | 2018-04-10 15:24:26 |
Message-ID: | 20180410152426.afy4pkfnm75pcjz7@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Steele wrote:
> 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.
Thanks!
> 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.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Chapman Flack | 2018-04-10 15:26:19 | Re: lazy detoasting |
Previous Message | David Steele | 2018-04-10 15:17:59 | 2018-03 CF Cleanup |