> Thanks for the tip. I didn't actually have anything to do with the > choice of Codestriker; I'm just the guy who got asked to add git > support. I think the decisions probably pretty solid at this point. > but I'll certainly suggest it and have a look. We're still > prototyping, so I suspect it'll be a while before [usefully] reviewing > every commit is at all feasible.
Something to consider too is possibly writing a post-commit script to automatically create topics. We do that at my work (we use subversion) and its quite handy. We have adopted a code review practice where we do post-commit reviews, and having a script to automatically create the topic saves a lot of time. We used to do pre-commits, but found this could become a bit of a bottleneck - especially as the team grew in size. Presumably this could be done with git too. Cheers, David ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Codestriker-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/codestriker-user
