Developer Info
General
Tips for ContributingChanges and creating SuccessfulPatches
ManagingBugs - how to work with the BTS
CompatibilityRules - how we keep our existing users from crying
OptionNaming - the conventions used to name command-line options
BasicCodingStyle - how to keep mpm from being grumpy with your code
WritingTests - how to add tests to the test suite
TranslatingMercurial - how to translate Mercurial into your own language
DevelopmentGuidelines - other things we try to follow when writing code
DeveloperRepos - where to find various public repositories of Mercurial work
NewFeatureDiscussions - A page of links to discussions about new features.
NewIdeas - Suggestions for features/extensions that would make someone happy
A list of Presentations and other related events.
MacOSXTools - Installing the tool chain on Mac OS X.
ProductName for the rules on using the name "Mercurial"
Modules in C
September 2008 posting by Matt about how to do initializers and error handling in C modules.
Mercurial internals
DeveloperBasics - some basic code examples
MercurialApi - The public API for Mercurial
Design - Mercurial's data structures and how it uses them.
WhatGoesWhere - the project architecture
FileFormats - list of Mercurial's disk file formats
WireProtocol - the push/pull changegroup protocol
DebuggingFeatures - how to poke around in Mercurial's internals
Theming - how to create new styles for Mercurial's web interface
WritingExtensions - how to write Mercurial extensions
Old stuff
First Mercurial UserSurvey.
The old ToDo list and MissingFeatures
The pre-1.0 RoadMap