April 28th, 2009
Which versioning tools to use for your project/application ? SVN or GIT
Imagine…you are working on a software project, there are loads of files and you are constantly making changes to it. Suppose, because of some modifiction the program stops responding or not working the way it should and its almost impossible for you to find the “needle” (error) from the haystack, what would you do ?!
Well I had numerous experiences such as this. After a lot of research I found out about CVS and SVN, GIT. These are methods to keep a version of your software from the time it is concieved, monitering every small change and till the time is done. The best part, if anything goes wrong, you can always revert back to the previous version.
This post is a small compilation of different versioning systems. I won`t be talking about CVS since it is kinda outdated and in the open-source community GIT or SVN is preferred.
What is SVN ? Why is it required ? You might be wondering. While developing applications for the web or any other area, most of us would be trying and testing the code on our local machines, sometimes it happens, while in the flow of coding, we tend to do some drastic changes to the sourcecode (atleast I do) only to find out that the application is not executing anymore after that. It becomes difficult to backtrack and eventually, we end up wasting a lot of time and energy, this is where SVN comes to our rescue.
