Differences between revisions 39 and 89 (spanning 50 versions)
Revision 39 as of 2008-05-19 22:25:31
Size: 2828
Editor: abuehl
Comment: how main and -stable are used, add subtitle for crew
Revision 89 as of 2017-09-06 20:41:33
Size: 3784
Editor: JunWu
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
This page lists [:Repository:repositories] used for Mercurial [:DeveloperInfo:development]. 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
 * 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
=== For End-users ===
 * https://www.mercurial-scm.org/repo/hg ("main") — the main repository for users, bleeding edge. A changeset needs 2 accepts from senior reviewers to get here.
 * https://www.mercurial-scm.org/repo/hg-stable — the stable repository, contains official releases with safe and important fixes applied, always a subset of the main repository
Line 8: Line 9:
Bugfixes are pushed to -stable, then pulled and merged to mainline. No new features are going to stable, mainline is pushed to stable after each release. === For Mercurial developers ===
 * https://www.mercurial-scm.org/repo/hg-committed — the main repository for developers, bleeding edge. A changeset needs 1 accept from a junior reviewer to get here. Do not use this repo unless you're a Mercurial developer. History in this repo is mutable.
Line 10: Line 12:
=== Crew repositories ===
 * http://hg.intevation.org/mercurial/crew – the [:CrewRepository] where main contributor queues changes for the main repository
 * http://hg.intevation.org/mercurial/crew-stable – queue with changes for hg-stable
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 [[TimeBasedReleasePlan|code freeze]].
Line 14: Line 14:
== Special Repositories == == Other core repositories ==
 * 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)
Line 16: Line 18:
 * http://hg.intevation.org/mercurial/tah – [:ThomasArendsenHein:Thomas Arendsen Hein]'s outgoing changes
 * http://hg.serpentine.com/mercurial/hg – [:BryanOSullivan:Bryan O'Sullivan]'s outgoing changes
 * http://oss.oracle.com/mercurial/ – Chris Mason's various repositories.
 * http://hg.omnifarious.org/~hopper/ – [:EricHopper:Eric Hopper]'s various repositories, including several Mercurial ones for various purposes.
 * http://hg.alexanderweb.de/ – [:AlexanderSchremmer:Alexander Schremmer]'s various repositories.
 * http://hg.kublai.com/ – [:BrendanCully:Brendan Cully]'s various repositories, including several Mercurial ones for various features he's developing, like the TransplantExtension and [http://hg.kublai.com/mercurial/branchview/ html branchview extension].
 * http://ohac.pun.jp/hg/ – [:HideyaOhashi:OHASHI Hideya]'s various repositories, including some patches for Mercurial.
 * http://hg.xavamedia.nl/ – DirkjanOchtman's various repositories, including a crew mirror with some extra changes that are in development.
The flow between the main and committed repositories is shown in this graph. The blue repositories are controlled by senior reviewers, the dark green repositories by core contributors and the light green repository by MartinGeisler.
Line 25: Line 20:
=== TortoiseHg ===
 * http://tortoisehg.sourceforge.net/hg/tortoisehg-dev – [:TortoiseHg] main repository
 * http://tortoisehg.sourceforge.net/hg/tortoisehg-crew – !TortoiseHg crew repository
 * http://hg.borho.org/tortoisehg-dev – SteveBorho's !TortoiseHg repository
{{{#!dot
digraph flow {
  subgraph {
    rank = source;
    "safe fixes" [shape = plaintext]
    "new features" [shape = plaintext]
  }
  translations [shape = plaintext]
Line 30: Line 29:
== Inactive Repositories ==   node [shape = box, style = filled]
Line 32: Line 31:
Repositories with no activity during the last 12 months:   subgraph {
    rank = same;
    "hg-stable" [fillcolor = cornflowerblue; URL = "https://www.mercurial-scm.org/repo/hg-stable"]
    hg [fillcolor = cornflowerblue; URL = "https://www.mercurial-scm.org/repo/hg"]
    "hg-committed" [fillcolor = limegreen; URL = "https://www.mercurial-scm.org/repo/hg-committed/"]
  }
Line 34: Line 38:
 * http://hg.thinkmo.de/mercurial/tw (see also http://hg.thinkmo.de/ for other stuff) – ThomasWaldmann's misc. changes
 * http://hg.intevation.org/mercurial/vadim – [:VadimGelfer:Vadim Gelfer]'s changes
 * http://archives.keltia.net/hg – [:OllivierRobert:Ollivier Robert]'s various repositories.
 * http://hg.beekhof.net/ – Andrew Beekhof's various repositories.
  subgraph {
    rank = same;
    "hg-i18n" [fillcolor = palegreen; URL = "http://bitbucket.org/mg/hg-i18n"]
    "hg-all" [fillcolor = limegreen; URL = "https://www.mercurial-scm.org/repo/hg-all/"]
  }

  "hg-stable" -> hg
  hg -> "hg-committed" [dir = back]
  hg -> "hg-i18n" [dir = back]
  hg -> "hg-all"
  "hg-committed" -> "hg-all"
  "hg-i18n" -> "hg-all"

  "safe fixes" -> "hg-stable"
  "safe fixes" -> "hg-committed"
  "hg-i18n" -> translations [dir=back]
  "new features" -> "hg-committed" [constraint = false]
}
}}}
== TortoiseHg ==
See the TortoiseHg Wiki page for that project's [[https://bitbucket.org/tortoisehg/thg/wiki/developers/repositories|development repositories]].

== Inactive repositories ==
Repositories that have been decommissioned or had no recent activity:

 * 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),
 * http://hg.intevation.org/mercurial/tah – This repository now contains the latest version tested and deployed by [[ThomasArendsenHein|Thomas Arendsen Hein]]. His outgoing changes go either to the devel list or directly to crew, so it is listed as inactive (for development purposes).
Line 40: Line 70:
CategoryContributing CategoryProject CategoryDeveloper

Developer Repositories

This page lists repositories used for Mercurial development.

Main repositories

For End-users

For Mercurial developers

  • https://www.mercurial-scm.org/repo/hg-committed — the main repository for developers, bleeding edge. A changeset needs 1 accept from a junior reviewer to get here. Do not use this repo unless you're a Mercurial developer. History in this repo is mutable.

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 senior reviewers, the dark green repositories by core contributors and the light green repository by MartinGeisler.

TortoiseHg

See the TortoiseHg Wiki page for that project's development repositories.

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)