Mercurial development workflow

[Martin Geisler]

Hi all,

I am new to distributed SCM systems and I am still trying to figure
out how changes flow between repositories.

So I would be interested in knowing how the development of Mercurial
itself is done. From the mercurial-devel mailinglist I see four
repositories in play:

  mercurial: http://www.selenic.com/hg/
  hg-stable: http://www.selenic.com/repo/hg-stable/

  mercurial/crew:        http://hg.intevation.org/mercurial/crew/
  mercurial/crew-stable: http://hg.intevation.org/mercurial/crew-stable/

By downloading the repositories and looking at them with 'hg view' hg
and crew seem identical, and likewise for hg-stable and crew-stable.
The hg-stable repository seems to be a subset of the hg repository
(likewise for crew-stable and crew).

Is this done by having people push stable and safe changes to the
{hg,crew}-stable repositories and then pulling these changes into
{hg,crew} whereas more unsafe changes are made in the {hg,crew}
repositories?

What if a change is made in hg and needs to be applied to hg-stable as
well? Do you then manually apply the patch to hg-stable?

Thanks in advance for any answers.

-- 
Martin Geisler  ---  <mgeisler at mgeisler.net>  ---  http://mgeisler.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20070729/3a0902db/attachment-0001.asc>