Using a Source Control is a requirement for software developer companies. There are too many source control available which store your data in a repository. In this article we will take a look at considerations to select a source control.
Title : Considerations to select a Source Control
Publish Date : 06/04/2010
Version : 1.0
Author : Nasser Hadjloo
Author Mail : firstname.lastname@example.org
Copyright (c) 2010 Nasser Hadjloo.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation;
with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled “GNU Free Documentation License”.
First of all you need a list of available source control for your platform. Surely you cannot use a Windows application in you Red Hat.
The next step is to remove some items from the provided list. Everybody can have different idea about removing attribute. For example for someone, using on the net is a must but for another one is not. So remove some item from your list to garble your list.
Now you have a list with 3 – 5 items. The next step is to specify your cost range. There are some expensive and some open source (free) item in your list. So decide to use remove some item with the cost range. Probably your list contains some fee and some free items.
Now you should take a look at your IDE and check if these items support your IDE or not. In some cases there are some third party add-ons for your source control which may integrate the source control with your IDE. So go and search for it.
The next step is to compare remained items feature.
If there are some items in your list yet, check for those communities on the web. And see which one/ones are used more in your similar case.
The next step is to attention to ease of use.
If there are some items in your list yet, you can ask your developers experience about remained item, and check what those think about remained items.
Finally you have to use remained Items in a test lab, and check if are those really good enough for you?
This is no matter which item you selected for your Source Control. The key point is that you really Garble some items and currently selected item is your choice. So learn it yourself and then learn it completely to your team. If your developers can not work with it change it, because you will face serious problems ASAP.
I check the web and Found GIT
– useful and with above steps for me TFS
was better than others. Because TFS
(2010) is integrated with Visual Studio, is light (2010 version), has a large community, is easy to use, has a web port, Microsoft is supporting it. The minus point for TFS
is that it’s expensive which this issue resolved in VS2010, cause it installs with VS2010 and whenever you install VS2010, you install it.
I wish TFS
became open source one day and became a category killer in it’s category. After TFS
I suggest GIT
and after that you can use from SVN