On Thu, Feb 9, 2012 at 21:54, Satish Balay <[email protected]> wrote:

I interpreted sean as suggesting using 'hg tags' to organize relase patches and dev changes in a single repo.

Release and dev in the same clone does not work (and was not suggested) unless bookmarks are used. Since that isn't familiar to a lot of Hg users, I'm not suggesting it.

And instead of using seprate clones for releases as we do now - redo the work flow with 'hg tags'

To me its not easy to implement branches with tags - hence the above statement. [either you have named branches or you let the repo have multiple heads - and keep tagging the release head and workarround the confusion during merges etc. I'd rather deal with these issues in separate clones for release/dev]

I think separate clone for release and dev is easy for people to work with. I think separate clones for every release is clutter.