How should I implement versioning within mercurial?

Question

Possible Duplicate:
How to use mercurial for release management?

What should I use for versioning my applications using mercurial? Should I use tags, branching, any other option? Right now I'm branching for every deployed version of my application with a name specifying which version it is. Am I doing it wrong? Is there a better solution?

Here's a history view of my repository:

enter image description here

There's already a dozen question here concerning which is the best way to manage release with Mercurial, for example : [How to use mercurial for release management?](http://stackoverflow.com/questions/3827628/how-to-use-mercurial-for-release-management) — krtek, Feb 12 '12 at 18:30

score 1 · Answer 1 · answered Feb 12 '12 at 14:24

1

I don't use Mercurial, but had plenty of experience with Perforce and can tell you what we did.

We would Label or Tag each build that was a release, but only branch if we needed to change it. This way you only add the additional overhead of a branch when you actually need to branch your code.

answered Feb 12 '12 at 14:24

Toby Allen

10,997
11
73
124

I wonder if your solution would be the same in Mercurial as it's implementation is different than other source controls – Jonas Stawski Feb 12 '12 at 14:33
The idea I think is the same as you can create a branch from a historical point. – Toby Allen Feb 12 '12 at 14:35

score 1 · Answer 2 · edited May 23 '17 at 10:30

You can already find a lot of various question about this exact topic. For example :

Hopefully you will find all the answers you need their ! You can also follow the various links provided in the "Related" secion on the right.

How should I implement versioning within mercurial?

2 Answers2