5 source control systems for distributed development teams


Published on

5 Source Control Systems for Distributed Development Teams

Published in: Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

5 source control systems for distributed development teams

  1. 1. 5 Source Control Systems for Distributed Development TeamsBy Justin JamesVersion control can be a big issue for developers working from various locations, but a gooddistributed control system can keep the project on track.If you have developers offsite or otherwise working in a disconnected manner, version control canbe a challenge. Traditional centralized version control systems like Team Foundation Server andSubversion use a central server to be a “single point of contact” and maintain a canonical versionof files, which is a tough paradigm for distributed teams to work with. Thankfully, a new breed ofversion control systems, called distributed version control systems, do away with the need for acentral repository (though you can make one if you want). These version control systems makelife easy for disconnected teams to work. Here are five that work well for teams spread across timezones and geographical areas.1: GitGit is one of the most popular distributed version control systems. Originally written by LinusTorvalds (and distributed under the GPL) to serve as the repository for Linux kernel development,it has gained widespread adoption among groups of individuals working together. For teams thatdo not want to handle their own server, Git is available from a number of providers, the most well-known of which is GitHub.2: MercurialMercurial is another excellent distributed version control system. I personally like it a lot,especially used in conjunction with the TortoiseHg plugin for Windows and the VisualHG pluginfor Visual Studio, which makes Mercurial as “built-in” smooth as Team Foundation Server. LikeGit, Mercurial is open source, and it has a number of commercial hosts like Bitbucket. Also ofinterest is Fog Creek’s FogBugz project, which adds bug tracking to Mercurial, and its Kilnapplication, which puts a ton of project management and team tools on top.3: CodePlexCodePlex is a source code hosting site run by Microsoft. While it is not a separate version controlsystem by itself (you can choose between Team Foundation Server and Mercurial hosting), it is setup to allow full project management. CodePlex can be used directly from Visual Studio, whichmakes it a good choice for .NET developers.4: BazaarMaintained by Canonical (the makers of Ubuntu Linux), Bazaar is one of the older distributed
  2. 2. version control systems, debuting right around the same time as Git. It too is open source and free,and can be used in a hosted offering (including SourceForge). Something that sets Bazaar apart isits ability to work well with other version control systems, even non-distributed ones like SVN,which makes it a good choice for remote workers on a project that’s using a centralized versioncontrol system.5: BitKeeperBitKeeper is the granddaddy of distributed version control systems. There was a good bit ofcontroversy around its licensing (it is not open source) and the use of it in the Linux Kernelproject. As a result, Linus Torvalds took a lot of the ideas he liked in BitKeeper and wrote Git.BitKeeper does not have any hosted versions that I can find, and it is proprietary softwarerequiring a paid license for commercial use.Recommend Office .NET/Silverlight Component:Spire.XLS for .NET and SilverlightSpire.Office for .NET and SilverlightSpire.Doc for .NET and SilverlightSpire.PDF for .NETSpire.DataExport for .NET