I think I'm missing part of this. What is the actual path to switching to GitHub? I've seen pages describing how individual development tasks will be converted from trac to GitHub, but what does the overall transition look like?
- Do we just say, before November 1 (or whenever) we're doing everything on trac, and after we're doing everything on GitHub? - Or is there a period where both are active and people can slowly transition? We have a GitHub page now; if the transition is approved, do people start creating issues and pull requests right away? - Or some other option? I apologize if this has been discussed and I missed it. On Saturday, September 24, 2022 at 10:09:46 AM UTC-7 Matthias Koeppe wrote: > On Saturday, September 24, 2022 at 9:27:46 AM UTC-7 mathzeta2 wrote: > >> Is it possible to choose the issue numbers in GH when making a migration? >> Then, setting a redirect of the form " >> https://trac.sagemath.org/ticket/$TICKET_NUMBER -> >> https://github.com/sagemath/sage/issues/$TICKET_NUMBER"; will make the >> lion's share of the links still relevant. >> > > Yes, to map it like this is the plan. > > >> This does not preserve fragments like "#comment:7", which is useful in >> long ticket discussions. >> > > Thanks, I've opened https://github.com/sagemath/trac-to-github/issues/7 > for this. > > > -- 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/9b4a5765-c00c-456e-bb11-67dbad37e19an%40googlegroups.com.
