On Saturday, August 6, 2016 at 2:28:40 PM UTC+2, Johan S. R. Nielsen wrote: > > We are informally and without tools abiding by the ticket-DAG.
Because there is no ticket-DAG and there is no immutable history of tickets. Ticket dependencies are informational but don't change what code is being added. Which is precisely why they can be mutable. 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. It seems that you want to erase history yet have it, too. You basically want a pre-commit review workflow, whereas we currently do post-commit review. Both are feasible but developers definitely need more experience with git in the former. -- 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.
