Workflow including restricting pushes to specific users

[greg fenton]

We're in the process of migrating from CVS to Hg.

Our current workflow is that all devs are free to push to HEAD (tip)
whenever.  As we near a release, we branch for that release and as the code
stabilizes we limit commits to senior developers.  Any juniors that have
fixes for the upcoming release sends patches to the seniors for
verification, merge and commit.

[We aren't just being pedantic, there are quite good reasons for this
approach.  Our environment is a hierarchically-based repository system,
often small changes have trickle effects that are not clear at all to junior
developers working at lower levels of the hierarchy.]

I've read over most of the Workflows I could find related to Mercurial.
 Some discuss centralized control.  Some discuss "branchy" development.
 Maybe I'm missing it, but I don't see any way we could move to something
like the above, restricting pushes on one branch while allowing full access
to others.

Thoughts and/or workflow descriptions you think I should be reviewing more
closely?

Thanks in advance,
greg.fenton
--
greg.fenton ^_at_^ gmail (yes, dot com)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100514/3157c996/attachment.html>