Sunday 20 April 2008 5:59:50 am
Hi Thomas and Bruce, GIT is not the only interesting VCS: Pro and Contra from the bazaar view:
http://bazaar-vcs.org/BzrVsGit
http://bazaar-vcs.org/BzrVsSvn
http://bazaar-vcs.org/BzrVsHg http://jam-bazaar.blogspot.com/2007/10/bazaar-vs-subversion.html We are still using SVN, but it does not fit well any more. Many different servers, eZ versions, PHP-Versions, extensions and extension versions, eZ patches, many different places, where the developer are and many OSses.
You need:
+ Different eZ versions
* Different PHP-Versions
* Different eZ extensions for different eZ versions and PHP Versions
* Different eZ extensions for one extension for different customer
* Different configurations for different servers, databases, server software (Apache, Lighty, OpenOffice, Red5, ffmpeg, imagemagick, for find and so on)
* Many different developer, companies each with projects of more than 5 years of development = uncountable complexity and the keep all these servers up to date with version control.
A software should adapt the human workflow and not the human the given software workflows. http://bazaar-vcs.org/Workflows @Bruce: As a result a community fork? This is a political point and not a point from VCS software. It is sometimes not easy to get important patches into the core and I think, many of us have patched versions running, but far, far away from a fork. Read "Decentralized systems do not encourage forking" http://bazaar-vcs.org/DecentralizedArguments And as a nice overview:
Intro to Distributed Version Control (Illustrated) http://betterexplained.com/articles/intro-to-distributed-version-control-illustrated/ Greetings ekke
http://www.coolscreen.de - Over 40 years of certified eZ Publish know-how: http://www.cjw-network.com
CJW Newsletter: http://projects.ez.no/cjw_newsletter - http://cjw-network.com/en/ez-publ...w-newsletter-multi-channel-marketing
|