Thanks, this is already in a pretty nice shape! I’ve extended some points a bit.
I think an explicit description of what will replace the states of a ticket (for example positive review) is still missing. In my opinion, we can also directly drop the develop branch and move to the master/main-branch only model. But that’s slightly orthogonal to the migration to Github. I would rather put such suggestions explaining what can be done after the migration is finished into a separate MD-File. tobias...@gmail.com schrieb am Sonntag, 11. September 2022 um 09:17:24 UTC+2: > On Saturday, 10 September 2022 at 21:32:50 UTC+2 Matthias Koeppe wrote: > >> On Saturday, September 10, 2022 at 8:12:48 AM UTC-7 Matthias Koeppe wrote: >> >>> I've added a draft of a proposed workflow on GitHub with the idea to >>> just follow the Trac workflow. >>> Help is welcome in adding links to documentation for the various bits. >>> >>> I think we can have a fleshed out Trac to GitHub transition guide by the >>> end of the weekend. >>> >>> >> A draft of the Trac-to-GitHub transition guide is now available at: >> https://github.com/sagemath/sage/wiki/migration-from-trac-to-Git**b >> >> Please let me know what's missing or unclear. >> >> > > Thanks, this is already in a pretty nice shape! I've extended some points > a bit. > > In my opinion, we can also directly drop the develop branch and move to > the master/main-branch only model. But that's slightly orthogonal to the > migration to Github. > -- 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/7bbb0a76-1c97-485b-a133-d44d21ec52e3n%40googlegroups.com.
