[Libclc-dev] Mailman->Discourse Migration on February 1, 10am PST
Tanya Lattner via Libclc-dev
libclc-dev at lists.llvm.org
Sat Jan 29 08:28:20 PST 2022
As referenced in this blog post <https://blog.llvm.org/posts/2022-01-07-moving-to-discourse/>, we are getting close to the deadline for migration for some Mailman lists to Discourse. If you are receiving this email from a LLVM Mailman list, then this list will be migrating to Discourse on February 1st.
We have gone through several test runs and feel that we are ready to do the final migration on February 1st starting at 10 am PST. Once the migration begins, the impacted Mailman lists and Discourse will be read only until it has completed.
Here are the steps of the migration process on February 1st at 10 am PST:
The Mailman lists that are migrating will be placed in “read-only” mode. No mail will be accepted to the list.
Mailman will be shut down while the final archives are collected. We expect this downtime to be about 15 minutes.
The mailman archives are sent to Discourse for migration (15-20 minutes for data transfer).
The LLVM DIscourse is put into read-only mode. Given the size of our archives, we expect the import to take 5 hours.
Sanity-checks will be made to ensure that everything looks as expected. We estimate this will take 1 hour or less.
The LLVM Discourse will be opened up again with all the archives imported.
We will post on Discourse about how things went and any next steps in the “Announcements” category.
We will use the Discourse Migration website <https://llvm.org/docs/DiscourseMigrationGuide.html> to communicate where we are in the process.
We expect the LLVM Discourse to open by 5pm PST, but realize that even in the best plans, there may be unexpected situations that arise that cause the migration to take longer or possibly be stopped. If that occurs, we will evaluate the best course of action and communicate to the community as described above.
If you have any questions, please let me know.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Libclc-dev