|
Size: 349
Comment:
|
Size: 3693
Comment: remove dead inactive repos; link to TortiseHg's repo page
|
| 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-tah - Thomas Arendsen Hein's outgoing changes * http://www.serpentine.com/hg/ - Bryan O'Sullivan's outgoing changes * http://hg.serpentine.com/mercurial/mq - Chris Mason's Mercurial Queues extension |
== Main repositories == * 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 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 == * 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. {{{#!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 = "http://selenic.com/repo/hg-stable"] hg [fillcolor = cornflowerblue; URL = "http://selenic.com/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 = both] hg -> "hg-i18n" [dir = both] 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] "new features" -> hg [constraint = false] } }}} == TortoiseHg == See the Tortoise``Hg 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
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
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-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.
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).