Geek asks and answers

When should I tag a revision in Mercurial

Can anyone give me any recommendations as to when I want to tag the revision in Mercurial.

For example, would it be nice to use them to indicate the points at which my application loads?

+3
source share
5 answers
  • When releasing / deploying, it is recommended that you tag the tag.
  • If you only need a bookmark, you can use a local tag.
  • If you need to specify a specific revision, for example, in an error report or email, just use the change set identifier, it is long, but you can shorten it.
+4
source

Here is a partial list when you can tag your code:

  • When deployed in an environment
  • .

, ( ), , .

+3

In our company, we use tags when deploying our applications on our servers.

+1
source

I think it's good practice to tag the codebase when it is released, and you will want to tag it also at the end of the sprint / development cycle.

+1
source

The release note is what the Mercurial project itself is:

https://www.mercurial-scm.org/wiki/StandardBranching

You can see the results here:

https://www.mercurial-scm.org/repo/hg/tags

+1
source

More articles:


All Articles