Ok so we all know the standard SVN set-up of
trunk\\
branches\\
tags\\
And I realize that the recommendation is that tags should have \"spe
Tags are not intended to be modified, you should make a branch if you want to do that.
You can make a branch from a tag, which is probably what you would want to do, then re-tag the results of that branch as a different version.
You shouldn't checkout a tag for editing.
You don't lose any history by branching(copying) in SVN. It all is linked together.
We used it to tag specific builds that were interesting but not releases, e.g.: "Investor Demo", etc.
In my experience tags are used for release markers, and where you aren't likely to make modifications.
If you create a "release2-0" branch, and then need to make changes (e.g. to fix a bug found post-launch) it no longer represents what you released for version 2.0.
If instead you create the "release2-0" tag and find you need to patch that version, you can create a new branch, make the fix there, and tag that as "release-2-0-1".
This way you can easily access any of your releases.