Veracity Q&A home login about faq

as title. thanks

asked Sep 21 '11 at 04:34

ijse's gravatar image


edited Sep 21 '11 at 07:46

Paul%20Roub's gravatar image

Paul Roub ♦♦

Tags are very much like tags in Git and Mercurial and label in Vault. You would use them to identity a group of files that are a part of a build or a release. The tag must be unique.

Stamps are very much like tags in other contexts in the internet. You would stamp a group of files as 'Stable', or 'Valid', much like we tag posts on this forum. Think of it as adding attributes to a set of files. More then one set of files can have the same stamp.


answered Sep 21 '11 at 07:46

acbova's gravatar image


edited Sep 21 '11 at 20:20

The simplest difference is that tags are unique, stamps are not.

Only one changeset can have a specific tag (such as RELEASE_1_0); attempting to apply that tag to another changeset without removing it from the first will cause an error.

Multiple changesets can share the same stamp, however - you might have several branches in a QA_REVIEW_NEEDED state, for example. Our team use a "goodbuild" stamp on any changeset which successfully built and passed automated unit tests.

Stamps can also be applied to work items, whereas tags are specific to version control.


answered Sep 21 '11 at 07:46

Paul%20Roub's gravatar image

Paul Roub ♦♦

edited Sep 21 '11 at 08:00

Joe%20Ream's gravatar image

Joe Ream ♦

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or __italic__
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported



Asked: Sep 21 '11 at 04:34

Seen: 1,451 times

Last updated: Sep 21 '11 at 20:20

powered by OSQA