More about Source control and random IT info
Some source control tools require a server and a client in order to be operational. Others only require a client. Still others work perfectly with a client that works as a local server as well. Please read the article on requirements gathering before deciding. In short: all depends on your set-up. Follow here for client …
Following software is available as a client: Clearcase Git Subversion CVS Visual SourceSafe Subversion, CVS and Visual SourceSafe allow file access to the local repository. For technical reasons, installing a local server on a drive mapping or file mapping on a server is not recommended. The risk on corruption is high. Clearcase, Git, Subversion and …
For a server, the most common platform should be Linux. It is stable, fast, easy, secured, does not require expensive machines and the free options are valid choices for all kinds of businesses. I see no single benefit for installing Windows for a server. Most of the time, after the initial set-up of the source …
People are using following systems: CVS 12,6% Git/GitHub 6,8% IBM Rational ClearCase 2,8% IBM Rational Team Concert 0,9% IBM Rational Telelogic Synergy Suite 0,2% Mercurial 3,0% Microsoft Team Foundation Server 0,8% Microsoft Visual SourceSafe 1,6% Perforce 3,0% Subversion 58,3% None – I don’t use a source code management system 5,6% Don’t know 1,4% Other (specify) …
Instead of deploying your own source control server, one can use some of the available source control repositories. On of the biggest is Sourceforge with 230000 projects and 3 million users. There are plenty of others. Depending on the hosting environment, you will need to use certain tools. Most of them support SVN. Depending on …
… continued from about page … In a previous life, I did administrate different repositories in different technologies. Those repositories were accessed by multiple people, and in some cases from different environments and different continents. From this experience, sometimes the hard way, I have developed 2 preferences: Subversion and Git. Both work reasonably well, both …
Following tools are available on windows: GIT SmartGIT, TortoiseGIT Subversion SmartSVN, TortoiseSVN Visual SourceSafe Visual SourceSafe client Clearcase Clearcase client CVS SmartCVS Command line tools are being disregarded because most windows users are not used to use command line tools.
Please go to the pages for the specific solutions for more information. I cannot give an advice on the best tool to use on linux. Please read the article on selecting the right tool for more information. Tool oriented information: GIT Subversion Use oriented information: Server install Source control client
Git on Mac OS X GIT Subversion
Overview of source control tools: System Project page (external) Market share (*) SVN / Subverison Apache subversion 55% CVS 12% GIT Official GIT site 7% Clearcase IBM Clearcase 3% VSS / Visual Source-safe Microsoft site 2% Mercurial Selenic site 2% TFS / Team foundation server Microsoft site 2% Bazaar Canonical site 3% Perforce 1% One …
English
Arabic
Chinese (Simplified)
Dutch
French
German
Italian
Portuguese
Russian
Spanish
Swahili