How to set up distributed version control in a company

From my experience with using distributed version control systems (DVCS), such as git and mercury in open source projects, most installation models use centralized configuration for their project (I think GitHub).

When you deploy distributed VCS in your company , do you have a centralized installation model ?

+5
source share
4 answers

It’s a good idea to have some kind of central repository, because it will allow you to exchange codes, but also have a branch somewhere from which you can directly create your assemblies / export your pictures. This server will likely have more than one branch, one of which is considered a trunk branch. Any previous releases will have their own branch and depending on the hierarchy of your team (i.e. if you are divided into groups with each group working on one aspect of the application), there may be branches based on the team or based on functions, although, if you do not work so that it is not necessary.

, , , . . , , , , - , - , "" , . . , "" , , .

VCS, , , DVCS , . , .

, . , , , .

DVCS, , Bazaar. Mercurial.

+4

, VCS, cetralized VCS.

, svn, . DVCS.

0

, , , , . , .

, DVCS , . , ( , ). , , , , .

, , . , . VCS .

, , , , . DVCS VCS . , VCS, , ( !) .

0

All Articles