Differences between revisions 10 and 91 (spanning 81 versions)
Revision 10 as of 2005-12-08 01:29:37
Size: 767
Editor: EricHopper
Comment:
Revision 91 as of 2017-09-06 20:57:56
Size: 3867
Editor: JunWu
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
These are repos for various Mercurial development: = Developer Repositories =
This page lists [[Repository|repositories]] used for Mercurial [[DeveloperInfo|development]].
Line 3: Line 4:
 * http://selenic.com/repo/hg
  * the main repository
 * http://hg.intevation.org/mercurial/crew
  * Temporary main repository
 * 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://www.serpentine.com/~cmason
  * Chris Mason's [:MqExtension:Mercurial Queues extension]
 * http://hg.omnifarious.org/~hopper/
  * [:EricHopper:Eric Hopper's] various repositories, including several Mercurial ones for various purposes.
 * http://hg.thinkmo.de/mercurial/tw (see also http://hg.thinkmo.de/ for other stuff)
  * ThomasWaldmann's misc. changes
== Main repositories ==
=== 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

=== 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. This repo contains history of the main repo as public changesets. Draft changesets in this repo are 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 [[TimeBasedReleasePlan|code freeze]].

== Other core repositories ==
 * http://bitbucket.org/mg/hg-i18n/ — translation updates are queued here by MartinGeisler (see TranslatingMercurial)
 * https://www.mercurial-scm.org/repo/hg-all/ — combined mirror of main & hg-committed & i18n

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.

{{{#!dot
digraph flow {
  subgraph {
    rank = source;
    "safe fixes" [shape = plaintext]
    "new features" [shape = plaintext]
  }
  translations [shape = plaintext]

  node [shape = box, style = filled]

  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/"]
  }

  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).

----
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. This repo contains history of the main repo as public changesets. Draft changesets in this repo are 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)