SVN (Trunk/Branch/Tag) - I
27 May 2008SVN (SubVersion) is being used in software development houses to maintain the source code. Its very effective if used properly. In this post, I will present some basic concepts about SVN.
Usually, SVN has following directory structure:
/trunk
/branches
/tags
You may add more directories like archive and some other of you want. I will explain the use of above directories so you know when to use what.
The trunk directory contains main line of development. If you need to checkout a project, you will do from here. The project copy from trunk is later released to the client.
Branch is a line of development that exists independently of another line, yet still shares a common history if you look far enough back in time. A branch always begins life as a copy of something, and moves on from there, generating its own history. For example, you may create a branch from trunk. You might be thinking, why we need that. Let me explain:
You are working on a project and you are assigned a task which can take 10 days. You want to checkin you changes to the trunk, once the task is full done because intermediate changes might not be very interesting and may introduce problems for others. If you simply don’t checkin, then its risky to keep the development only on you machine. The solution is to create a branch and work keep checking in to that. In this way, you will have all your work in the repository and it won’t be bothering any one.
Continued …
Related Posts:
Top Of Page | Trackback
If you found this page useful, consider linking to it. Simply copy and paste the code below into your web site.
It will look like this: SVN (Trunk/Branch/Tag) - I
