Request for comments about using named branches to track releases

[Ike Casteleyn]

Hi Mario,


In my company we use a variant of your option 1.

The big difference is that we have multiple stable branches at the same time.

We use .net, our version is in the assemblyinfo.cs that gets updated when we start a release build.


What you describe to me, comes across as you only have one version of your software you need to maintain at the same time.

This reminds me of a branch model from nvie.

http://nvie.com/posts/a-successful-git-branching-model/

<http://nvie.com/posts/a-successful-git-branching-model/>Yes, this is for git, but you can do this workflow in mercurial too (I even think you can find extensions for it, although you can do it manually).

This might give you a new look/insights at your branching model.


Question that popped up when reading your post:

- Do you really need a version for the dev branch? Is a version (that matters) not always created from the stable branch?

- In option 1, after a release a merge to the dev-branch should happen (version in dev-branch will be updated accordingly)

- Don't you need to stabilize your dev-branch before merging to stable? (this is where nvie comes in handy)


Best regards,

Ike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20171006/03b3205c/attachment-0002.html>