Tag a Release

What does it mean to tag a release? Why is it important to do this before testing?

torikhet
Profile Answers by torikhet Questions by torikhet
Apr 5th, 2009
4
5300

Questions by torikhet

QA Testing

Answer

Editorial / Best Answer

kurtz182

Profile Answers by kurtz182 Questions by kurtz182

Member Since Nov-2009 | Dec 15th, 2009

One feature common to all version control systems is the ability to label or tag a release. Effectively, this provides a virtual “snapshot” of the state of all files at the time a release is built. In some systems like Clearcase, a label is attached to files, while in others, like Subversion, a label (or tag) is presented as a separate ‘directory’ in the repository. In either case, both allow you to turn the clock back to the moment of a release and rebuild things as they were at that time.

Showing Answers 1 - 4 of 4 Answers

leo4rakesh
Profile Answers by leo4rakesh

Apr 15th, 2009

As far as I know, this means that a minor release must assure full compatibility with previous minor releases and you can guess why it is important by seeing the answer. As before any minor release it is very important to check the builds compatibility with the previous released builds. I hope am correct...

kurtz182
Profile Answers by kurtz182 Questions by kurtz182

Dec 15th, 2009

One feature common to all version control systems is the ability to label or tag a release. Effectively, this provides a virtual “snapshot” of the state of all files at the time a release is built. In some systems like Clearcase, a label is attached to files, while in others, like Subversion, a label (or tag) is presented as a separate ‘directory’ in the repository. In either case, both allow you to turn the clock back to the moment of a release and rebuild things as they were at that time.