I like to use SVN and specially their client for Win XP TortoiseSVN. But still didn’t use all the functionality which it gives. Here is very nice tutorial done by BEA.
Because I didn’t know what is the difference between tagging and branching here some thoughts I have found:
- you can name it as you want aka release_1.0
- it will take snapshot of all files and their revision number
- CVS will increase revision number for file(s) we are committing to repository, so we have to somehow keep information of all revision numbers of all files.
- SVN A tag is just a “snapshot” of a project in time. In Subversion, this idea already seems to be everywhere. Each repository revision is exactly that—a snapshot of the filesystem after each commit. Advantage of having tag command in SVN is that you can put name like release_1.1 instead of 673.
- when your software goes to production, tag it.
- then you continue programing. But during time, customer finds some bugs. So what to do ? Just checkout on to some other folder your code but with revision/tag name release_1.0. You will get your code which customer has and you can repair it, commit it back to your “release_1.0” revision and delivered the build to customer
- Next you will repair your code in your HEAD revision.
- Branches allows you to work on code which was already delivered