Mercurial - team review of changeset prior to remote repo push

We have multiple developers working on our app.

We'd like to review a developers code prior to pushing that to the remote repo.

How can we distribute the changeset for review without pushing it to the remote开发者_开发问答 repo (and having other dev's pull and review from the remote repo)?

Update: Had thought about just having the developer share their local repository. Not sure exactly how to do this on Windows.. I see shared disk mentioned on the linked doc.. not clear how to set that up..

Update 2: Figured out that hg serve worked as a nice way to share the repo.. see answer below.

Maybe you can use a intermeditate review repo where developers push their code for review, and once checked, from that repo is pused to the remote repo.

Update: There is also a lot of code review tools that can help you, or you may work with Pull requests and some tool like one2merge to aprove them after the reviewers see the changes and comment on them.

We used hg serve to allow the developer to share her repository using Mercurial's built in web server. Other developers cloned their local repository then pulled in the changes in question from the developer's repo using hg pull http://1.2.3.4:8000

One option is to emulate open-source projects and send out changesets for review via email. Benefits include:

• No need for yet another repo/server
• The patch is sent for review via email, so any number of reviewers can be copied
• A traceable history of the code review is archived in email

See the patchbomb and mbox extensions for details.