| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Date: | 2019-06-20 17:53:08 |
| Message-ID: | CA+TgmobK3TVoxNJ0vCwvLcAjjaLvMLFWcbEpWA042bT9VdVWfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Thu, Jun 20, 2019 at 1:28 PM Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> I suppose we could have a moratorium on commits starting from (say) EOB
> Wednesday of the week prior to the release; patches can only be
> committed after that if they have ample support (where "ample support"
> might be defined as having +1 from, say, two other committers). That
> way there's time to discuss/revert/fix anything that is deemed
> controversial.
Or we could have a moratorium on any change at any time that has a -1
from a committer and a +1 from nobody.
I mean, your idea is not bad either. I'm just saying.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2019-06-20 18:24:07 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Alvaro Herrera | 2019-06-20 17:28:38 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2019-06-20 18:20:27 | Re: Tweaking DSM and DSA limits |
| Previous Message | Alvaro Herrera | 2019-06-20 17:28:38 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |