> You are trying to build a DAG of tickets that is a coarser version of the > git DAG. You'd need > > * Tools to make sure that the two different graphs stay alined. > * UI to visualize the two different graphs, and to report conflicts > * Documentation
We are informally and without tools abiding by the ticket-DAG. If it wasn't for the stupid git-behaviour of throwing-away-single-commits-info when you do commit-squasing, I would suggest squashing all commits to single tickets upon merging. That would make the history and git-blame work much nicer. I would only wish for best-effort tools that would * work as expected in the expected case. * possibly report on the ticket-DAG vs. git-DAG violations. In the current discussion, the best-effort tool I'm talking about is pretty simple (if e.g. there was a single dependency, you would just report "git diff <that_dependencys_branch>") > All that for the (at best minor, possibly questionable) advantage of > reviewing tickets whose base is not yet reviewed. Why don't you just review > tickets in order? Of course I do this. But I also review tickets in parallel. Have you not ever worked on a ticket that depended on another ticket not yet merged?! > Do you want your reviews being thrown away because the base changed? Of course! Best, Johan -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
