Source management

we create hospital information system software. The project will differ from hospital to hospital and contain various use cases. But many parts will be the same. Therefore, we will use a branching source control mechanism. If we find a mistake in one hospital, how can we know that the other branches have the same error or not.

IMAGE http://img85.imageshack.us/img85/5074/version.png

The numbers in the picture that we attached show each hospital software.

Do you have a solution to this problem?

What control source (SVN, Git, Hg) is suitable for this problem?

Thank.!

+1
source share
2 answers

, VCS, - , , , commom.

, , , , , . , , - .

, , , , - :

-, ( ), , , ( ​​ ).

( ), :

  • , - , .
  • , , .

, , - , , , -, , , .

, , , Inversion of Control Dependency Injection, . ( .NET, Managed Extensibility Framework - MEF), "" , .

, - , , , , .

, , - @VonC - , , , .

, , , ​​(, , /), / , -

... Microsoft, TFS, .

( ), DVCS (Mercurial, Git, Bazaar ..), , . , SVN - ( , ), , - , -, Continuous Integration Server, - DVCS , , " " , DVCS, , , ( , , )

, VCS, , , .

0

VCS (Version Control System) " ", , :

CVCS ()

DVCS ()

, DVCS.
, , :

  • , .
  • , , ( , )
0

Source: https://habr.com/ru/post/1747366/


All Articles