From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org, pgsql-www(at)postgresql(dot)org |
Subject: | Re: Schedule for migration to pglister |
Date: | 2017-11-06 15:43:15 |
Message-ID: | 20171106154315.GK4628@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Tom,
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > Each list will receive an email with a link to the wiki about the
> > migration after the list has been migrated.
>
> I suggest doing that the other way 'round. Otherwise, the email
> about the change will inevitably go into a lot of peoples' bit
> buckets if they haven't adjusted their mail filters yet.
My thought had been to do before-and-after, but I got complaints from
others that we'd then be spamming a lot of people with email.
We definitely need one after the migration because the new mail *won't*
end up caught in people's filters, and for those who intentionally
filter the list traffic into the garbage because they couldn't figure
out how to unsubscribe, this is going to be most annoying (this is what
we saw with the pgadmin lists and it was quite painful).
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Jim Van Fleet | 2017-11-06 15:44:24 | Re: [POC] Faster processing at Gather node |
Previous Message | Magnus Hagander | 2017-11-06 15:42:49 | Re: [HACKERS] Schedule for migration to pglister |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-11-06 15:46:24 | Re: [HACKERS] Schedule for migration to pglister |
Previous Message | Magnus Hagander | 2017-11-06 15:42:49 | Re: [HACKERS] Schedule for migration to pglister |