|
Size: 4327
Comment:
|
Size: 3784
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 * 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: |
| == Stable repository == * The best way to get the latest stable version is to follow this example: * hg clone http://selenic.com/repo/hg * cd hg * hg up stable (this takes you to the stable branch) * make local |
=== 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 15: | Line 12: |
| At the time of writing, this should make a [[http://mercurial.selenic.com/wiki/WhatsNew#A1.5_-_2010-03-06|1.5]] stable version of Mercurial. | 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 17: | Line 14: |
| 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. | == 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 19: | Line 18: |
| === Crew repositories === * http://hg.intevation.org/mercurial/crew – the CrewRepository where 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) 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 29: | Line 22: |
| "new features" [shape = plaintext] "safe fixes" [shape = plaintext] |
subgraph { rank = source; "safe fixes" [shape = plaintext] "new features" [shape = plaintext] } |
| Line 35: | Line 31: |
| "hg-stable" [fillcolor = cornflowerblue] hg [fillcolor = cornflowerblue] |
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 38: | Line 38: |
| "crew-stable" [fillcolor = limegreen] crew [fillcolor = limegreen] "hg-i18n" [fillcolor = palegreen] |
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/"] } |
| Line 44: | 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 50: | Line 52: |
| "safe fixes" -> "crew-stable" "new features" -> crew [constraint = false] "new features" -> hg [constraint = false] |
"safe fixes" -> "hg-committed" |
| Line 54: | Line 54: |
| "new features" -> "hg-committed" [constraint = false] | |
| Line 56: | Line 57: |
| == Special Repositories == * 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. |
== TortoiseHg == See the TortoiseHg Wiki page for that project's [[https://bitbucket.org/tortoisehg/thg/wiki/developers/repositories|development repositories]]. |
| Line 66: | Line 60: |
| === TortoiseHg === * http://bitbucket.org/tortoisehg/stable – TortoiseHg main repository |
== Inactive repositories == Repositories that have been decommissioned or had no recent activity: |
| Line 69: | Line 63: |
| == Inactive Repositories == Repositories with no activity during the last 12 months: * 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/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 78: | Line 70: |
| CategoryContributing | CategoryProject CategoryDeveloper |
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. 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
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 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).