: One thing to think about is if you develop on trunk and forget to merge to : 4.x, thats ok. the other way around is bad though, it basically creates an : instant regression. : : So I'm a little worried about this. I think development should be against : trunk!
+1 ... for me it's never been a question of the tools -- i've never trusted the merge props to help keep anything straight. I'm first and foremost concerned about features/fixes making it into 4x that then vanish when 5x comes out. Knowing that "logical commits" are only flow in one direction (even if the physical bits being changed are different) is really helpful for keeping sane ... particulaly when you start seeing test failures in 4x but not trunk, or vice versa: The number of possible causes doubles when there's a chance someone made a logical commit to 4x that never made it to trunk (was a bug committed to X but not Y? was a fix committed to Y but not X?) -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
