I’ve been using SVN for some time now, and am pretty happy with how it works (but I can’t say I’m an expert, and I haven’t really done much with branches and merging). However an opportunity has arisen to put in some new practises on a new team and so I thought I’d take a look at DVCSs to see if it’s worth making the jump.
The company I work for is a pretty standard company where we all work in the same location (or sometimes at home) and we want to keep a central store of all code.
My question is: if all you are doing with a DVCS is creating a central hub that everyone pushes their changes to, is there really any benefit to moving to a DVCS and its extra overheads in this sort of environment?
With DVCS’s people can maintain their own local branches without making any changes in the central repository, and push their changes to the master repository when they think it’s cooked up. Our project is stored in an SVN repository but personally I use git-svn to manage my local changes and find it quite useful, because we are not allowed to submit all the changes immediately(they have to be approved by the integrator first).