|
Size: 4667
Comment:
|
← Revision 91 as of 2017-09-06 20:57:56 ⇥
Size: 3867
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]]. 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 |
=== 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 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. |
=== 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. |
| Line 12: | Line 12: |
| === Crew 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 [[TimeBasedReleasePlan|code freeze]]. |
| Line 14: | Line 14: |
| * https://www.mercurial-scm.org/repo/hg-committed/ – where main contributors push draft change for the main repository, * 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 == * 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 |
| Line 21: | Line 18: |
| 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. | 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 26: | Line 23: |
| rank = sink; "new features" [shape = plaintext] } subgraph { |
|
| Line 32: | Line 25: |
| "new features" [shape = plaintext] | |
| Line 39: | Line 33: |
| "hg-stable" [fillcolor = cornflowerblue; URL = "http://selenic.com/repo/hg-stable"] "crew-stable" [fillcolor = limegreen; URL = "http://hg.intevation.org/mercurial/crew-stable"] |
"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 45: | 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 49: | Line 44: |
| "hg-i18n" [fillcolor = palegreen; URL = "http://bitbucket.org/mg/hg-i18n"] |
|
| Line 52: | Line 45: |
| "hg-stable" -> "crew-stable" [dir = both] "crew-stable" -> crew hg -> crew [dir = both] hg -> "hg-i18n" [dir = both] |
hg -> "hg-committed" [dir = back] hg -> "hg-i18n" [dir = back] hg -> "hg-all" "hg-committed" -> "hg-all" "hg-i18n" -> "hg-all" |
| Line 58: | Line 52: |
| "safe fixes" -> "crew-stable" "new features" -> crew [constraint = false] "new features" -> hg [constraint = false] |
"safe fixes" -> "hg-committed" |
| Line 62: | Line 54: |
| "new features" -> "hg-committed" [constraint = false] | |
| Line 64: | Line 57: |
== Special repositories == * https://hg.plav.in/clones/hg_my — [[AlexanderPlavin|Alexander Plavin]]'s work in progress for [[SummerOfCode/2013]] === TortoiseHg === * https://bitbucket.org/tortoisehg/thg/ – [[TortoiseHg]] main repository |
== TortoiseHg == See the TortoiseHg Wiki page for that project's [[https://bitbucket.org/tortoisehg/thg/wiki/developers/repositories|development repositories]]. |
| Line 74: | Line 61: |
| Repositories that have been decommissioned or had no recent activity: | |
| Line 75: | Line 63: |
| Repositories with no activity during the last 12 months: | * 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 77: | Line 69: |
| * 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.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. * 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). * 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://hg.xavamedia.nl/ – DirkjanOchtman's various repositories, including a crew mirror with some extra changes that are in development. |
Developer Repositories
This page lists repositories used for Mercurial development.
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 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.
TortoiseHg
See the TortoiseHg Wiki page for that project's 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 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).