Differences between revisions 80 and 84 (spanning 4 versions)
⇤ ← Revision 80 as of 2015-01-08 10:06:31 →
Size: 4534
Editor: ChingisDugarzhapov
Comment: broken link
← Revision 84 as of 2016-05-11 20:03:10 → ⇥
Size: 4781
Editor: KevinBullock
Comment: fix description of inactive repos
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]].
Line 12: Line 12:
=== Crew repositories ===
 * http://hg.intevation.org/mercurial/crew – the [[CrewRepository]] where main contributors queue changes for the main repository
 * http://hg.netv6.net/clowncopter/ – Where facebook main contributors queue changes for the main repository
 * http://hg.intevation.org/mercurial/crew-stable – changesets of the branch named `stable` are pushed here automatically.
 * http://hg.intevation.org/mercurial/crew+main – automatic mix of crew and main (may contain multiple heads).
 * http://bitbucket.org/mg/hg-i18n/ – translation updates are queued here by MartinGeisler (see TranslatingMercurial)		 == Other core repositories ==
Line 19: Line 14:
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.  * https://www.mercurial-scm.org/repo/hg-committed/ — where core contributors push draft changes for the main repository
 * https://www.mercurial-scm.org/repo/hg-all/ — combined mirror of main & hg-committed
 * http://bitbucket.org/mg/hg-i18n/ — translation updates are queued here by MartinGeisler (see TranslatingMercurial)

The flow between the main and committed repositories is shown in this graph. The blue repositories are controlled by Matt, the dark green repositories by core contributors and the light green repository by MartinGeisler.
Line 24: Line 23:
    rank = sink;
    "new features" [shape = plaintext]
  }
  subgraph {
Line 30: Line 25:
    "new features" [shape = plaintext]
Line 38: Line 34:
    "crew-stable" [fillcolor = limegreen; URL = "http://hg.intevation.org/mercurial/crew-stable"]     hg [fillcolor = cornflowerblue; URL = "http://selenic.com/repo/hg"]
    "hg-committed" [fillcolor = limegreen; URL = "https://www.mercurial-scm.org/repo/hg-committed/"]
Line 43: Line 40:
    hg [fillcolor = cornflowerblue; URL = "http://selenic.com/repo/hg"]
    crew [fillcolor = limegreen; URL = "http://hg.intevation.org/mercurial/crew"]		     "hg-i18n" [fillcolor = palegreen; URL = "http://bitbucket.org/mg/hg-i18n"]
    "hg-all" [fillcolor = limegreen; URL = "https://www.mercurial-scm.org/repo/hg-all/"]
Line 47: Line 44:
  "hg-i18n" [fillcolor = palegreen; URL = "http://bitbucket.org/mg/hg-i18n"]
Line 50: Line 45:
  "hg-stable" -> "crew-stable" [dir = both]
  "crew-stable" -> crew
  hg -> crew [dir = both]		   hg -> "hg-committed" [dir = both]
Line 54: Line 47:
  hg -> "hg-all"
  "hg-committed" -> "hg-all"
  "hg-i18n" -> "hg-all"
Line 56: Line 52:
  "safe fixes" -> "crew-stable"
  "new features" -> crew [constraint = false]		   "safe fixes" -> "hg-committed"
  "hg-i18n" -> translations [dir=back]
  "new features" -> "hg-committed" [constraint = false]
Line 59: Line 56:
  "hg-i18n" -> translations [dir=back]
Line 73: Line 69:
Repositories with no activity during the last 12 months: Repositories that have been decommissioned or had no recent activity:
Line 75: Line 71:
 * http://hg.intevation.org/mercurial/crew – the [[CrewRepository]] where main contributors used to queue changes for the main repository,
 * http://hg.netv6.net/clowncopter/ – Where Facebook main contributors used to queue changes for the main repository,
 * http://hg.intevation.org/mercurial/crew-stable – changesets of the branch named `stable` are pushed here automatically,
 * http://hg.intevation.org/mercurial/crew+main – automatic mix of crew and main (may contain multiple heads),

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.

Other core repositories

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

Special repositories

TortoiseHg

Inactive repositories

Repositories that have been decommissioned or had no recent activity:

CategoryProject CategoryDeveloper

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