Hi all, I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. Migrating arch-commits could be a challenge though (+1 million mails) and just deprecating it would be easier :) So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way? [1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/59 Cheers, Kristian Klausen
Am Sun, 15 May 2022 23:53:31 +0200
schrieb Kristian Klausen
Hi all,
I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. Migrating arch-commits could be a challenge though (+1 million mails) and just deprecating it would be easier :)
So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way?
[1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/59
Cheers, Kristian Klausen
I always keep a few months back of this list locally and would like to keep it until we have a better place to watch all commit changes. It's the fastest way to get full Arch "ChangeLog" and check what package could have lead to breakage and what other packagers are doing. -Andy
El domingo, 15 de mayo de 2022 23:53:31 (CEST), Kristian Klausen escribió:
So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way?
I do use it to monitor commits, so I'd appreciate if the list was kept. I do not care about the archives and IMHO it doesn't make much sense to waste resources on migrating it or saving it from now on, as it essentially duplicates svn log. For comparison, the equivalent KDE list https://mail.kde.org/mailman/listinfo/kde-commits also doesn't save archives.
Hi,
I also would like to keep it to monitor the repositories.
Thanks.
greetings
tpowa
Am So., 15. Mai 2022 um 23:53 Uhr schrieb Kristian Klausen
Hi all,
I'm in the process of migrating our mailing lists from mailman2 to mailman3[1]. Migrating arch-commits could be a challenge though (+1 million mails) and just deprecating it would be easier :)
So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way?
[1] https://gitlab.archlinux.org/archlinux/infrastructure/-/issues/59
Cheers, Kristian Klausen
-- Tobias Powalowski Arch Linux Developer & Package Maintainer (tpowa) https://www.archlinux.org tpowa@archlinux.org St. Martin-Apotheke Herzog-Georg-Str. 25 89415 Lauingen https://www.st-martin-apo.de info@st-martin-apo.de
On 15.05.2022 23.53, Kristian Klausen wrote:
So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way?
So from the response I got so far, it sounds like the archive isn't used. If I don't get any new responses in the next few days, I will just migrate arch-commits to mailman3 without migrating the archive and with archiving disabled. Cheers, Kristian
On 17.05.2022 19.27, Kristian Klausen wrote:
On 15.05.2022 23.53, Kristian Klausen wrote:
So, is there any reasons for not deprecating it? How are you using it and could that need be met in some other (and perhaps better) way?
So from the response I got so far, it sounds like the archive isn't used.
If I don't get any new responses in the next few days, I will just migrate arch-commits to mailman3 without migrating the archive and with archiving disabled.
This is now implemented. Cheers, Kristian
participants (4)
-
Andreas Radke
-
Antonio Rojas
-
Kristian Klausen
-
Tobias Powalowski