On Mon, Sep 12, 2022 at 11:10 AM Kwankyu Lee <ekwan...@gmail.com> 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? > > 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?
Indeed, a complete import of tickets is not an easy task - however, we can build upon experiences of other projects, such as CPython, for this. See e.g. https://discuss.python.org/t/github-issues-migration-is-coming-soon/13791/4 Once we are able to work on tickets on github, we'd switch trac to read-only mode, which requires less computational resources, so it will be cheaper to run. Dima > > -- > 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/e3c966c0-c65a-4b91-8133-a5e66340a26bn%40googlegroups.com. -- 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/CAAWYfq3U%2BkrYbW%3D7hu0oaZHz%3DtfQm0CqcW1up%2BddpS8vjaUz4A%40mail.gmail.com.
