title: DVCS - tag multiple revisions
body: <p>I have in mind such release workflow:<br>
   - One branch is a <code>trunk</code> branch - it may has sub-branches for features and other purposes.<br>
   - Second branch is <code>stable</code> - it represents releases for production.<br>
   - Revisions of <code>trunk</code> - are tagged for versions of releases. If I want to make a release - I must nominate one or multiple changesets for release version and then merge them into <code>stable</code>, and end final revision of this multi-merge will be a new <code>stable</code> version.<br></p>
  
  <p>There is an options - use some external tool for track to which version revisions are belong, or write this information in commit-messages - but I don't like them, because I want to store this information in DVCS, and not depend on any external software for release management.</p>
  
  <p>And so my questions is:<br>
   - Is it good scheme at all?<br>
   - Is there such tool for any popular DVSC, for mass-tagging of revisions?<br></p>