On Sat, Jan 19, 2019 at 01:19:46PM -0500, Stephen Frost wrote:
> * Magnus Hagander (magnus@hagander.net) wrote:
> > On Fri, Jan 18, 2019 at 4:02 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > > Magnus Hagander <magnus@hagander.net> writes:
> > > > On Fri, Jan 18, 2019 at 1:26 AM Michael Paquier <michael@paquier.xyz>
> > > wrote:
> > > >> Wouldn't it be better to also switch the references to pgsql-bugs in
> > > >> all the C code for the different --help outputs?
> > >
> > > > You are right, we definitely should. I'll go ahead and fix that. I can't
> > > > quite make up my mind on if it's a good idea to backpatch that though --
> > > > it's certainly safe enough to do, but it might cause issues for
> > > translators?
> > >
> > > Yeah, weak -1 for back-patching. We don't usually like to thrash
> > > translatable messages in the back branches.
> >
> > Pushed.
>
> 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?
