- accepted (by the CCC)
- The stage of the CCC process after "DRAFT", and "PROPOSED". At this stage the primary goals are to ensure that the proposed changes are suitable for the release in a general sense and that the requisite JCK and SQE resources will be available.
- approved (by the CCC)
- The stage of the CCC process after "FINAL". The CCC has approved the final version of the request which permits push into the the project forest.
- A collection of changes with respect to the current clone of a repository.
- development freeze
- The date by which all planned work should be complete for a particular line of development. After a line's development freeze, only exit-criteria bugs may be fixed in that line.
- A collection of Mercurial repositories which can be managed as
a set of nested repositories. The name "Forest" originally came
from the Mercurial "Forest Extension" which can be used with some
versions of Mercurial, but in general is no longer recommended. The
make/scripts/hgforest.shcan be used to apply a Mercurial
hgcommand to all the repositories in a forest.
- A collection of individuals who engage in open conversation about a common interest. That interest may be in the creation, enhancement, or maintenance of a specific body of code or it may lie in other areas, e.g., quality, documentation, or evangelism. See the group overview.
- A free, cross-platform, distributed source management tool. Source bundles and binary packages for Mercurial are available at http://www.selenic.com/mercurial/wiki/index.cgi. The main Mercurial documentation is available at http://hgbook.red-bean.com.
- A collaborative effort to produce a specific artifact, which may be a body of code, or documentation, or some other material. See the project overview.
- A directory tree in the filesystem that Mercurial treats specially. This tree contains the source files and their revision history.