[CentOS-announce] [Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read

-----BEGIN PGP SIGNATURE-----

wsF5BAABCAAjFiEExbC4H21L30WoH1yeol26+xfzt6EFAmYMFVAFAwAAAAAACgkQol26+xfzt6HQ
pxAAvkaYQYSfVU6BOvLCQ+FB/OTrY3LSPnfYrBZAeanURkp8ssBeJCLw/OMYdz3r2RI2MEzK1oga
AgnTZLUffkpO4ViNW8RVnrkctuxAxhFfkoksrOhGH1PZhcXUXqLNCyngp5vAF9yYtz5TZF9jatZE
FfdCx4bU6jhLyvTCWp5Aqo/DPNyQ31nvpFfAqHcBHgW2oZu+bo8rq6+HhqesWioCsiZH5tlb2xiM
hcy5r+u+LYuB5wK06zFHmNiepbmTCO56G3/suhfyTWYY2A84Nkghrr01xYLUJAQJMvmbCr2PBIKb
Op7G/cEHDd9UWDWV1q/gM3QLQeyeIgAzNUcb2ww4Wo+Htk62uLM2Rj0a0i5IadAHDPv10KsxGD/7
HjHYBWUG+rvaKWQGxfVttmx8PRirdgjK2jwH3GLcxJioQxtJOGhP/xGD+fsjXSmpM1nHJzKXZOWn
DGNX1/hXOYG8vSuOFnoVV71tGIpsV1k7MkqXTDU6+oD2eeRxh3vyiTxHLVHL8FoDe4pTMn2wj7I2
uLIPFVsVcQG/oeGqJXHQ7W9BextHnPyr+tP5VlgNNYeoefwWgLJAbUMmH3J7jG1yTen3xB1tAwQh
7/aOiMI0AGrbs376/L80bBsNfADlaxT8bm2q5hAehcUVTdHN4qTAS+9hv/hURRWtz3WHSJjSdz1+
mzg=
=sWes
-----END PGP SIGNATURE-----
Due to a needed upgrade , we'll have to move the existing CentOS
mailman instance (aka https://lists.centos.org) to a new server/host.

Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""".
You can convert to local time with $(date -d '2024-04-08 07:00 UTC')

The expected "downtime" is estimated to ~60 minutes , time needed to :
- take last mailman2 backup
- reimport / convert mailman2 archives to mailman3 DB
- DNS propagation for A/AAAA/MX records

Here are also some important information about the mailman2 => mailman3
migration :

# Renamed lists
Worth knowing that, based on open discussion on the centos-devel list
(see whole thread at
https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html),
existing lists will be *renamed* , so while we'll put aliases for
incoming mails, each list member will start receiving list mails from
new list name. So start updating your filters if you filter on email
address instead of "subject:"

Here is the overview of the new lists names :

arm-dev at centos.org => arm-dev at lists.centos.org
centos at centos.org => discuss at lists.centos.org
centos-devel at centos.org => devel at lists.centos.org
centos-announce at centos.org => announce at lists.centos.org
centos-automotive-sig at centos.org => automotive-sig at lists.centos.org
centos-{cz,de,es,fr,nl,pt-br,zh}@centos.org =>
discuss-{cz,de,es,fr,nl,pt-br,zh}@lists.centos.org
ci-users at centos.org => ci-users at lists.centos.org
centos-gsoc: => gsoc at lists.centos.org
centos-mirror at centos.org => mirror at lists.centos.org
centos-mirror-announce at centos.org => mirror-announce at lists.centos.org
centos-newsletter at centos.org => newsletter at lists.centos.org
centos-promo at centos.org => promo at lists.centos.org
centos-virt at centos.org => virt at lists.centos.org


# Authentication
Mailman2 had no real concept of authentication so you could just
subscribe to one or more lists, and have a password associated with your
email address for that/these subscription(s).
Mailman3 itself is split into "core" and "webui" components, so when
we'll import mailman2 lists/config into mailman3, your existing
subscriptions will continue to work *but* not your password.

Mailman3 will be configured to support SSO, and so if you already have a
FAS/ACO account (https://accounts.centos.org) you'll be able to login
directly into new webui and manage your settings/subscriptions *if* your
ACO email address of course matches the one you initially subscribed
with for lists.centos.org.

If that's not the case, either create an ACO/FAS account that will match
and you'll be then able to "link" your mailman3 account with FAS and so
manage your settings/subscriptions.

If you don't want to, there is always the documented process :
https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account


Thanks for your understanding and patience.

on behalf of the Infra team,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]