I would propose that we target Feb 1, 2023 as the day on which we switch from Trac to GitHub. This gives us more than 1 month for inspecting the converted issues and fine-tuning the conversion.
I've updated https://trac.sagemath.org/ticket/30363 and https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b On Sunday, December 25, 2022 at 2:08:34 PM UTC-8 Matthias Koeppe wrote: > All 35000 converted issues are now available for inspection in > subdirectories like Issues-33xxx > <https://github.com/sagemath/trac_to_gh/tree/main/Issues-33xxx> in > https://github.com/sagemath/trac_to_gh > > On Sunday, December 25, 2022 at 3:36:23 AM UTC-8 Kwankyu Lee wrote: > >> The migration script accesses the Trac server via XMLRPC and does not >>> need privileged access. The first conversion of our 35000 tickets takes >>> about 8 hours. The migration script keeps a disk cache for the Trac data, >>> so later conversions are fast, enabling quick iterations when fine-tuning >>> the conversion script. >>> >> >> Hence all developers are recommended to try to run the conversion script >> for their favorite (open and closed) tickets, and check if the conversion >> is done correctly. If you spot a conversion error, please report it to >> >> https://github.com/sagemath/trac-to-github/issues/18 >> >> -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/1bebf016-d3b6-45b4-a2d4-5726f4310c73n%40googlegroups.com.
