Mercurial

Mercurial
Name	Mercurial
Author	Matt Mackall
Developer	Mercurial community
Released	2005
Programming language	Python, C
Operating system	Cross-platform
License	GNU GPL v2

Mercurial Mercurial is a distributed version control system created for managing source code and coordinating changes across projects such as Mozilla Foundation, Python (programming language), OpenJDK, Linux kernel-related efforts, and Apache Software Foundation projects. It competes in the same space as Git and Bazaar (software), and influenced workflows used at organizations like Facebook, Google, Microsoft, Canonical (company), and FLOSS communities. Mercurial emphasizes performance, simplicity, and extensibility, and has been used in large-scale projects including OpenStack, Eclipse Foundation, FreeBSD, and Nokia-related repositories.

History

Mercurial was created in 2005 by Matt Mackall during a period of heated development around BitKeeper alternatives after disputes involving Linus Torvalds and Linux kernel contributors; contemporaneous projects included Git by Torvalds and Bazaar (software) by Canonical. Early adoption occurred among groups such as Mozilla Foundation, Python (programming language), and OpenSolaris contributors. Over time the project governance shifted through entities and events like Python Software Foundation interactions, community-driven contributions from developers associated with Google, Facebook, and various academic institutions, and infrastructure collaborations with hosts like Bitbucket and Heptapod-related efforts in the GNU Savannah and GitLab ecosystems. Notable milestones intersected with releases and compatibility efforts tied to PEP discussions and interoperability debates with GitHub and Launchpad.

Design and features

Mercurial's architecture centers on a content-addressable store and changelog model comparable to designs in Git and concepts from Monotone (software), with features supporting atomic commits, named branches, and extension hooks that integrate with systems such as Subversion, CVS, and Perforce. It provides file history, merge tracking, rebasing, and patch series workflow support similar to tools used by GNU Project, Free Software Foundation, and projects like OpenStack and Eclipse Foundation; built-in capabilities include revision identifiers, manifest structures, and delta storage analogous to innovations in Git and research from academic groups at institutions like MIT and Stanford University. The design emphasizes correctness and reproducibility, with attention to cross-platform behavior on Microsoft Windows, macOS, and Linux distributions maintained by organizations like Red Hat and Debian.

Command-line interface and extensions

The Mercurial command-line interface exposes commands like commit, push, pull, clone, merge, and bisect, paralleling idioms familiar to users of Git, Subversion, and CVS; it integrates extension hooks for systems developed by entities such as Canonical (company), Atlassian, GNU, and Python Software Foundation contributors. A rich extension ecosystem includes extensions for Git interoperability, large file support comparable to Git LFS, code review integration with Gerrit, Phabricator, and Review Board, and hosting integrations used by Bitbucket, GitLab, and Heptapod. Extensions have been developed by contributors affiliated with Mozilla Foundation, Facebook, Google, Intel, and various open source foundations, enabling workflows with tools like Jenkins, Travis CI, CircleCI, and Azure DevOps.

Development workflow and branching models

Mercurial supports multiple branching models including named branches, anonymous branches via bookmarks, and topic-branch workflows similar to practices at Linux kernel maintainers, Mozilla Foundation, and OpenStack contributor communities. Common workflows mirror those used at GitHub and GitLab—feature branch, pull request, and patch queue models—and have been adapted into policies at organizations like Canonical (company), Eclipse Foundation, and Apache Software Foundation projects. Code review, continuous integration, and release engineering practices employing Mercurial have been documented in cases from Mozilla Foundation, OpenStack, and academic research groups at University of California, Berkeley and Carnegie Mellon University examining collaboration patterns.

Implementation and performance

Mercurial is implemented primarily in Python (programming language) with performance-critical components in C for tight loops and hashing, echoing hybrid-language approaches used in projects from Google and Red Hat. Its storage format and delta application algorithms draw on techniques researched at institutions like MIT and Stanford University and share conceptual commonalities with implementations in Git and Monotone (software). Performance tuning and benchmarking have been carried out in contexts involving large monorepos at companies like Facebook, Google, and Microsoft, and in open source projects hosted by Mozilla Foundation and Debian maintainers to evaluate clone, checkout, and merge throughput on diverse platforms including FreeBSD, NetBSD, and enterprise Linux distributions from Red Hat.

Adoption and ecosystem

Mercurial has been adopted by a range of organizations and projects including Mozilla Foundation, Python (programming language), OpenJDK, OpenStack, Eclipse Foundation, Bitbucket (historically), and various academic and corporate research projects from Intel, IBM, and Nokia. Hosting, tooling, and migration services around Mercurial have been provided by platforms and vendors such as Atlassian, GitLab, Heptapod, and consulting firms that supported migrations alongside Canonical (company) and Red Hat. The ecosystem includes integrations with continuous integration solutions like Jenkins, Travis CI, CircleCI, and Azure DevOps, and GUI clients developed by contributors associated with TortoiseSVN-style projects and independent developers.

Security and licensing

Mercurial is distributed under the GNU General Public License version 2, aligning its licensing with many GNU Project initiatives and enabling contributions from organizations like Mozilla Foundation, Python Software Foundation, and Canonical (company). Security considerations have been addressed through advisory processes and patches contributed by developers from Google, Facebook, Red Hat, and community maintainers, and deployment practices have been influenced by incident responses at Mozilla Foundation and enterprise teams at Microsoft and IBM. Compatibility and auditability of repository formats have been important for compliance and forensics in contexts involving OpenStack, Eclipse Foundation, and government-funded academic collaborations at University of Oxford and ETH Zurich.

Category:Version control systems