Differences between revisions 81 and 82
Revision 81 as of 2016-03-21 21:02:20
Size: 4667
Comment:
Revision 82 as of 2016-05-11 19:43:02
Size: 4640
Editor: KevinBullock
Comment: rewrite description of main+stable
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
This page lists [[Repository|repositories]] used for Mercurial [[DeveloperInfo|development]]. See also [[MercurialDevelopmentProcess]]. This page lists [[Repository|repositories]] used for Mercurial [[DeveloperInfo|development]].
Line 5: Line 5:
 * 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/)
 * http://selenic.com/repo/hg-stable – the stable repository, solely managed by mpm, contains official releases with safe and important fixes applied, always a subset of the main repository
 * http://selenic.com/repo/hg ("main") — the main repository, bleeding edge, solely managed by mpm who often pulls from other repositories (mirrored at http://hg.intevation.org/mercurial/)
 * http://selenic.com/repo/hg-stable — the stable repository, solely managed by mpm, contains official releases with safe and important fixes applied, always a subset of the main repository
Line 8: Line 8:
Bugfixes are committed to the branch named `stable` and pushed to the main repository. Bugfixes are committed to the `stable` branch and pushed to the main repository.
Line 10: Line 10:
No new features are going to the stable branch, mainline (the default branch) will be branched again near each release. New features go to the `default` branch, which gets merged into `stable` at the start of each [[TimeBasedReleasePlan|code freeze]].

Developer Repositories

This page lists repositories used for Mercurial development.

Main repositories

Bugfixes are committed to the stable branch and pushed to the main repository. This branch is automatically pushed to hg-stable to provide a separate repository. New features go to the default branch, which gets merged into stable at the start of each code freeze.

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)