| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: commitfest 2018-07 |
| Date: | 2018-06-05 00:42:24 |
| Message-ID: | 20180605004224.GA5164@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 04, 2018 at 07:16:33PM -0400, Peter Eisentraut wrote:
> Per decision from the developer meeting, there will be a commitfest
> 2018-07 (unless there are concerns from the RMT).
Thanks for raising the thread.
> Could we set up the commitfest app appropriately?
Sure. I have admin rights for that so I could do it.
> There were some discussions about renaming the existing 2018-09 entry
> versus inserting a new one at -07 and requiring patches to be moved back
> explicitly.
I would do that to reduce unnecessary log noise, but I was unsure of the
actual status we are at. I am pretty sure that nobody is going to
complain if what they submitted gets looked up two months earlier than
what was previously planned, so I would vote to rename the existing
2018-09 to 2018-07, to rename the existing 2018-11 to 2018-09, and to
create three new CF entries.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2018-06-05 00:55:10 | Make deparsing of column defaults faster |
| Previous Message | Joshua D. Drake | 2018-06-05 00:36:18 | Re: Code of Conduct plan |