DVCS blessed repo replication among geographically distributed teams
My company is exploring the move from Perforce to a DVCS and we currently use lots of Perforce proxies because the software development teams are spread over Germany, China, USA and Mexico and sometimes bandwidth from one place to another is not that great.
I am a git user confused by mercurial’s branching. How am I supposed to track small changes?
I’ve always used git before, but I want to contribute to python so now I have to learn mercurial and I find it very frustrating.
Is a code review which uses only code comments a good idea?
In case of some question/issue reviewer create comment with special label, like “REV”. Such label MUST not be in production code — only on review stage:
Is a “model” branch a common practice?
I just thought it could be a good thing to have a dedicated version control branch for all database schema changes and I wanted to know if anyone else is doing the same and what have the results been.
Why not commit unresolved changes?
In a traditional VCS, I can understand why you would not commit unresolved files because you could break the build. However, I don’t understand why you shouldn’t commit unresolved files in a DVCS (some of them will actually prevent you from committing the files).
Is Perforce as good at merging as DVCSs?
I’ve heard that Perforce is very good at merging, I’m guessing this has to do with that it tracks changes in the form of changelists where you can add differences across several files in a single blow. I think this implies Perforce gathers more metadata and therefore has more information to do smarter merging (at least smarter than Subversion, being Perforce centralized).
Why can Perforce be a better version control system? [closed]
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for […]
What’s so difficult about SVN merges?
Possible Duplicate:
I’m a Subversion geek, why should I consider or not consider Mercurial or Git or any other DVCS?
Branching breaks continous integration?
I think this article, A Successful Git Branching Model, is very well known among experienced DVCS users.
Shorter release cycle with DVCS
Does the choice of using a DVCS over a CVCS actually make for shorter release cycles? If so, what makes software release cycles shorter and what are the arguments for this?