Tags are a vital part at Version Controlling for example SVN.
- When should i write Tags at SVN?
- What information should have a Tags?
|
Tags are a vital part at Version Controlling for example SVN.
|
|||||||||
|
It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.
|
Yes, Tags are vital part at Version Controlling for example SVN. When should i write Tags at SVN? Tags are for releases or stable versions of the code. When you comments out a branch to trunk, then you should write Tags. What information should have a Tags? As Tags are for releases or stable versions of the code, you can place most release note information at Tag. Following resource related to release note, which may help you to write Tags. Good Practices of writing release notes For naming convention of Tags http://stackoverflow.com/questions/2915399/svn-naming-convention-repository-branches-tags |
||||
|
|
When you want to give some revision some any special name, which contain more information, than plain revision number
Any, which you want. Mostly, it have to answer question "why it was tagged" |
|||
|
|