tracking daily changes, as a peon, in a clearcase shop

Question

I am struggling with a perceived conflict between tracking all my changes so I can figure out where I broke the code yesterday, and having a controlled (high overhead) code

Answer 1

I'm with tanascius and Stephen. Just because you use mercurial to track personal changes doesn't mean you cant submit earlier to ClearCase for review. The problem isn't mercurial or ClearCase it's submitting 4780 lines of code for someone to review.

I also work in a shop with strict review policies and Perforce. I use git to track local small changes but I still send off for review before the change gets to big for my co-workers to comprehend it.

Commit early and commit small.