At my company we are trying to add code reviewing practices into our development process and for that purpose we decided to use Review Board.

While Review Board should work out of the box for Subversion the workflow for Mercurial looks a little bit involved. Firstly it seems that only post reviewing(via post-review script) is supported for this type of repo. Secondly documentation is unclear whether post-review actually supports Mercurial(it only mentions git).

Could you folks describe your workflow in detail please?

Am I right in my thinking it should be something like this:

Developer:

1. clone master repo
2. clone feature repo from local master repo
3. hack-hack in feature repo
4. commit into feature repo
5. somehow run post-review from feature repo against parent master repo

Reviewer:

1. review diff
2. if OK then pull to the master repo from the feature repo