On Monday, September 12, 2022 at 3:10:54 AM UTC-7 Kwankyu Lee wrote: > According to > https://trac.sagemath.org/ticket/30406#comment:15 > trac continues to be running after migration to keep links to trac alive. > > Then do we really need to migrate (copy) tickets to github once and for > all? I guess that the migrated tickets would be full of broken links > internal or external. No? >
The migration script would rewrite the links. This will of course have to be checked before we go live with the converted repo. > Instead of having broken copies, why don't we keep the old tickets in > trac, and start only new tickets fresh in github. The release manager would > just declare to accept only PRs from github and reject branches of tickets > from trac. Then people would just start to make new tickets in github > mirroring tickets in trac. Gradually github will replace trac in all > development activities, without broken links. No? > In my opinion, it's crucial to make a full migration that converts the full history to the new format. Leaving it to developers to switch back and forth between the systems whenever they need to refer to the past is exactly the kind of friction that we want to avoid. -- 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/c67c25c1-7cc9-4367-ae34-59851357ad65n%40googlegroups.com.
