version control - Mercurial: Branching for releases? -



version control - Mercurial: Branching for releases? -

previous history: lastly couple of years used svn. releasing new version of software project included next steps:

creating branch new release: /repo/branches/0.1 getting code release-worthy state there creating tag release candidate: /repo/tags/0.1-rc1 creating branch rc1 prepare bugs: /repo/branches/0.1-rc1 creating tag new release candidate: /repo/tags/0.1-rc2 {...} creating tag v0.1 lastly rc: /repo/tags/0.1 merging 0.1 trunk

as far got mercurial sees branches , tags different svn , leads question:

do create branches (and tags) releases? , if not: else wants mercurial me doing archive similar described development pattern/cycle?

you can maintain using method. i'm not sure you'd need separate rc1 branch for, guess there reasons.

there bit of annoyance in way tags stored in mercurial, versioned file listing them 1 one. result tag creation constitutes changeset. should strive maintain such tag-creating changesets on 1 branch, or merge conflicts (which resolved, annoying nonetheless).

version-control mercurial release

Comments

Popular posts from this blog

formatting - SAS SQL Datepart function returning odd values -

c++ - Apple Mach-O Linker Error(Duplicate Symbols For Architecture armv7) -

php - Yii 2: Unable to find a class into the extension 'yii2-admin' -