Decentralized version control (DVCS) keeps track of software revisions and allows many developers to work on a given project without necessarily being connected to a common network.

learn more… | top users | synonyms

4
votes
4answers
370 views

Understanding my dvcs workflow

We are going to be building a new project using Mercurial as our version control system. I'm still trying to fully understand what my workflow should look like, so I've listed below a case that I ...
3
votes
2answers
495 views

Are any companies moving from DVCSs to CVCSs? [closed]

Are there any actual business cases that have made any company move from a DVCS to a CVCS (regardless of whether they were on a CVCS originally)?. Other than having a closed mind and rejecting the ...
3
votes
4answers
329 views

Will adopting a DVCS mean there will be a positive impact on development speed?

I was wondering how safe is to say that —because developers are free to version and have better and more organic workflows— code will be delivered faster. A big factor here is team size of course, ...
2
votes
2answers
221 views

Is it an absolute must that we ignore/delete all compiled files before committing?

I am working on a Drupal theme. I am going to be using "intermediary" languages to develop it, ie Stylus for styles, and CoffeeScript for some of the front-end scripts. I am going to be using a git ...
2
votes
1answer
179 views

Can DVCSs enforce a specific workflow?

So, I have this little debate at work where some of my colleagues (which are actually in charge of administrating our Perforce instance) say that workflows are strictly a process thing, and that the ...
2
votes
3answers
457 views

Release Management Tools with DVCS (Mercurial)

My development team is migrating from SVN to Mercurial. Having researched DVCS best practices, it has been suggested that we develop against feature branches of the repo mainline, test them ...
2
votes
1answer
336 views

Why aren't there cherry-pick requests?

One disadvantage to pull requests is lots and lots of merge commits. It's not the worst thing, but it does clutter the commit logs, and make for lots of unnecessary non-sequential history. A - C - E ...
1
vote
2answers
226 views

Will the customer benefit from a DVCS in any way?

Some of us can say a Distributed Version Control System (e.g. Mercurial, git) will have a positive impact on developers only out of the experience of using one (under the right conditions: higher ...
1
vote
2answers
400 views

What can be done to stop losing resources and unify Mercurial and Git? [closed]

Both Mercurial and Git were created as a replacement for the same program and to solve the same problem which you can read about in Martin Beckett's answer to How did Git and Mercurial develop so ...
0
votes
1answer
924 views

Setting up CI with [Jenkins, TeamCity, etc] - which source code control? [closed]

I am bound and determined to setup CI at work. I have played with Jenkins, and will download TeamCity when I get home (damn you work enforced download filters!) I have no IT support, and only so much ...
-2
votes
1answer
536 views

Why can Perforce be a better version control system? [closed]

I've seen some people love and some loathe Perforce. As users or administrators with experience with other version control systems (free cookie to the ones with DVCS experience [git, Mercurial]), what ...