| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Schedule and Release Management Team for PG10 |
| Date: | 2017-03-29 19:38:07 |
| Message-ID: | 20170329193806.jjxfcdm433qzs5yv@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Wed, Mar 29, 2017 at 3:04 PM, Alvaro Herrera
> <alvherre(at)2ndquadrant(dot)com> wrote:
> > I was rather surprised to see the March commitfest declared to exactly
> > one month and feature freeze immediately thereafter.
>
> That's true, but at
> https://wiki.postgresql.org/wiki/PgCon_2016_Developer_Meeting we
> agreed on March 31st as the feature freeze date. I don't think the
> RMT should substantially vary a date that was agreed by a developer
> meeting with wide attendance; that seems like the tyranny of the few
> over the many.
Yes, I agree with that -- which is why I didn't comment when I read the
minutes several weeks ago. I'm not proposing to change them, only
raising the point hoping that perhaps we'll choose differently next time.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-03-29 19:58:40 | Re: error handling in RegisterBackgroundWorker |
| Previous Message | Dave Page | 2017-03-29 19:34:54 | Re: Schedule and Release Management Team for PG10 |