From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Noah Misch <noah(at)leadboat(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pgsql: Remove references to Majordomo |
Date: | 2019-01-28 16:40:15 |
Message-ID: | CA+TgmoYiQS4PQZY4hjhPMNYBKHR=q2x3O3Ai-=9BD4YkfO5cTw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On Sun, Jan 27, 2019 at 2:28 AM Noah Misch <noah(at)leadboat(dot)com> wrote:
> > Does this also implicitly mean we've just agreed to push back the
> > retirement of the @postgresql.org aliases for the lists until v11 is
> > EOL..?
> >
> > I can understand the concern around translators and back-patching and
> > such, but I don't think we should be waiting another 5 years before we
> > retire those aliases as having them is preventing us from moving forward
> > with other infrastructure improvements to our email systems.
>
> What are those blocked infrastructure improvements?
+1 for that question. I find myself wondering what infrastructure
improvements could possibly be important enough to justify rushing
this change (or for that matter, ever making it at all).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-01-28 17:01:08 | Re: pgsql: Remove references to Majordomo |
Previous Message | Peter Eisentraut | 2019-01-28 13:48:43 | pgsql: doc: Add link from sslinfo to pg_stat_ssl |
From | Date | Subject | |
---|---|---|---|
Next Message | Jesper Pedersen | 2019-01-28 16:47:37 | Re: pg_upgrade: Pass -j down to vacuumdb |
Previous Message | Fabrízio de Royes Mello | 2019-01-28 16:30:49 | Re: pg_upgrade: Pass -j down to vacuumdb |