On Tuesday, September 13, 2022 at 3:30:19 PM UTC+9 Matthias Koeppe wrote: > On Monday, September 12, 2022 at 10:25:57 PM UTC-7 Travis Scrimshaw wrote: > >> whereas with trac, things are highly concentrated on tickets, which are a >>>> single point of reference. Using the GH/GL model, we have all of these >>>> forks >>>> >>> >>> Irrelevant because in the proposed workflow you never look at another >>> developer's fork. >>> >> >> This is not true. You do not have a central point for branch access. Now >> because of PRs that get attached to the main project, they do become >> centralized. >> > > Yes, in the proposed workflow everything goes through PRs. > > Yes, GitHub, like git, can also be used for other development workflows, > but such other workflows are not part of the proposal. Hence irrelevant. > > How is the workflow that our current developers sometimes use irrelevant? Granted, this is a less used feature, but I believe it makes it harder to share branches privately. It has been useful for me in the past to have this (e.g., some hacked together code meant only to be shared with collaborators).
-- 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/3fb68342-7efb-42d6-8163-89905bb557e3n%40googlegroups.com.
