I never really have had a problem with the new workflow (in fact, I actually prefer it to the old one). However I had a good command of git coming into this and read the "git the hard way". So my 2 cents would be to have developers spend time learning git properly instead of using the dev scripts (I think this is a useful skill beyond Sage development). However I do see your point that this is an extra barrier to Sage development since IMO one generally needs to know more about git than about Hg in order to development.
1) Put "Merged in" back. > +1 I'd also suggest not closing/merging tickets until shortly before releasing the next beta. > 2) Fix just how much crazy stuff shows up in "git log", presumably by > merging things differently or with different messages or something. > I don't think there's much we can do about this considering how git workflows are suppose to work and since the develop does have everything merged in. 4) Get http://trac.sagemath.org/ticket/14372 in. > +1 Best, Travis -- 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 http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
