Differences between revisions 59 and 63 (spanning 4 versions)
Revision 59 as of 2010-06-21 07:37:28
Size: 4211
Editor: JulianCowley
Comment: use rank constraints to avoid crossed edges
Revision 63 as of 2010-10-15 09:04:57
Size: 4276
Editor: abuehl
Comment: recat and style fixes
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
= Developer Repositories = = Developer repositories =
Line 5: Line 5:
 * http://selenic.com/repo/hg – the main repository, bleeding edge, solely managed by mpm who often pulls from other repositories  * http://selenic.com/repo/hg – the main repository, bleeding edge, solely managed by mpm who often pulls from other repositories (mirrored at http://hg.intevation.org/mercurial/)
Line 35: Line 35:
    rank=same;     rank = same;
Line 41: Line 41:
    rank=same;     rank = same;
Line 63: Line 63:
== Special Repositories == == Special repositories ==
Line 77: Line 77:
== Inactive Repositories == == Inactive repositories ==
Line 85: Line 85:
Line 87: Line 86:
CategoryContributing CategoryProject CategoryDeveloper

Developer repositories

This page lists repositories used for Mercurial development. See also MercurialDevelopmentProcess.

Main repositories

Bugfixes are committed to the branch named stable and pushed to the main repository. This branch is automatically pushed to hg-stable to provide a separate repository. No new features are going to the stable branch, mainline (the default branch) will be branched again near each release.

Crew repositories

The flow between the main and crew repositories is shown in this graph. The blue repositories are controlled by Matt, the dark green repositories by crew and the light green repository by MartinGeisler.

Special repositories

TortoiseHg

Inactive repositories

Repositories with no activity during the last 12 months:


CategoryProject CategoryDeveloper

DeveloperRepos (last edited 2017-09-06 20:57:56 by JunWu)