Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • This is what I was going to post, pretty much. You should certainly see productivity improvements from developers committing early and often to their own repository, without causing any trouble for any of their co-workers. Commented Jan 7, 2011 at 4:19
  • 5
    Then you'll be in integration hell when you eventually do push your changes. This is a bad thing not a good thing. Commented Jan 7, 2011 at 4:48
  • As you are doing local development with lots of commits you can continue to pull changes from the central repository and keep your local changes in line with the ongoing development that others are working on. Thus when it comes time to push your changes to the central repository you should already have the majority of the changes that have been happening there and integration will be easy. Commented Jan 7, 2011 at 9:58
  • 1
    Unless one of your coworkers has done the exact same thing and both of you haven't integrated for quite awhile. There is always trade off. I do have seen cases where stuff had been integrated on the mainline where they shouldn't have been (wrong solution, dead-end attempt at a solution and such), integrating at feature completeness has it's perks also. Commented Jan 7, 2011 at 14:10
  • 2
    Can't you do all of these things with (a) SVN branches or (b) multiple working copies? Commented Jan 7, 2011 at 14:29