Capistrano, Mercurial and branches

It is my understanding that although Mercurial has support from branches, the community generally clone repos instead of creating branches. Similar to the Darcs model, unlike the Git model.

I'm deploying a Ruby on Rails app with Capistrano and there I'd like to separate the production from the development branch. Should I point Capistrano to a different repo or sho开发者_JAVA百科uld I use branches?

Has anyone used one model or the other of branching while dealing with Capistrano? Any problems with either?

---

yes mercurial supports several branching models cloning is probably the most common.

this certainly sounds like the ideal use of a named branch to me, but its ultimately a personal preference thing

---

In your config/deploy.rb put

set :branch, "your_branch"