title: Mercurial Best Practices - Branch on Feature/Task?
body: <p>I just switched to Mercurial from SVN. I've done some basic stuff (importing my code, making commits, getting the hang of log/commit/revert/etc.) and read some tutorials on branching/merging.</p>
  
  <p>My question now is: <strong>What's the best ("Mercurial") way to use Mercurial?"</strong> I don't want to follow SVN paradigms; I want to do things the "right" way.</p>
  
  <p>I should mention that I'm a sole developer on most of my projects, and I'm using agile/scrum practices. Maybe my question should really be <strong>should I be cloning/branching per feature? Per task?</strong> I remember reading that this should be the case for Git, and this allows you to essentially keep multiple copies working at the same time and separate features vs. bug-fixes vs. whatever (i.e. keep your working copy separate for each different thing that you're doing). And it's also apparently part of <a href="https://www.mercurial-scm.org/wiki/WorkingPractices" rel="nofollow noreferrer">Mercurial's best practices</a>.</p>
  
  <p>Or I could just keep one copy, make my changes, and commit prolifically. Whatever.</p>
  
  <p>If this question is too subjective, I don't mind closing it, provided someone can link me to some reading materials on <em>how</em> to use Mercurial best. That's what I'm after.</p>