2. Convert all tickets to Issues in a new repo. (This preserves the ticket > numbers as Issue numbers.) >
Would it make sense to convert tickets with branches directly to pull-requests? Since most of them probably already contain quite a bit of discussion about the implementation, which you would like to have as a easy reference if you would review the PR later. > 4. Replace sagemath/sage by the new repo. > If you rename a repo (in our case sage -> sage-old), then github adds redirects for issues etc in sage to sage_old. So it should be double-checked that you can later indeed add a new repo with the name sage. -- 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/6418ac37-a858-447a-be9f-f7d7f4da9461n%40googlegroups.com.
