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
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.
Repositories that have been decommissioned or had no recent activity:
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).