(Use https://dev.mutt.org/ for encrypted access to this site.
The SSL certificate is self-signed; a PGP-signed copy of it is attached to this page.)

= Mutt developer resources =

== Bug tracking system ==

This trac exists mostly for its bug tracking database: report:3

To add new tickets or comment on tickets, you must be logged in (this is to protect the database from spam). You can register immediately using the link on the menu bar.''Note'': a valid email address is required (the registration page incorrectly states that it is optional) -- this is to send you a confirmation link. Sorry about that, we'd turn it off if the spammers would let us. Note that bug entries are forwarded to the mutt developer's list, making the email address you register with semi-public.

When reporting new tickets, please make sure that

  * you find a short but meaningful summary
  * describe a procedure for others to reproduce the problem (if possible)
  * select properties carefully, especially the priority, component and type fields
  * add "patch" to the keywords field when you have a proposed solution

See DebugTips for things to do to help diagnose a bug so that we can fix it faster.

== Documentation ==

Browse the [http://dev.mutt.org/doc/manual.html manual] for the development version, updated nightly.

== Code ==

The source code is maintained in a [http://selenic.com/mercurial/ Mercurial] repository
[http://dev.mutt.org/hg/mutt/ here]. You can pull your own copy for hacking with
{{{
hg clone http://dev.mutt.org/hg/mutt#HEAD
}}}
This will clone only the `HEAD` branch (where mainline development happens. You can omit the `#HEAD` to clone the entire repository,
but then you will need to use another command to check out the latest version into your working directory after the clone:
{{{
hg update -C HEAD
}}}
Afterwards, `hg pull -u` should keep you up to date.

Note that if you make local clones of the repository, they will revert to the "default" branch unless you explicitly specify #HEAD again while cloning. Use "hg summary" to check you are on the HEAD branch.
{{{
$ hg clone mutt-pristine-tree#HEAD myfeature-tree
$ cd myfeature-tree
$ hg summary
parent: ...
branch: HEAD
...
}}}


== Nightly snapshots ==

Download a nightly snapshot of the mutt distribution [http://dev.mutt.org/nightlies/ here]

== Release roadmap ==

The [/roadmap roadmap] has the current list of bugs blocking the release of Mutt 1.6.
There is also a TODO for the next point release [wiki:ReleaseToDo here].

== Developer Resources ==

The mutt source contains some developer resources in the {{{contrib/}}} subdirectory, namely:

  * [http://dev.mutt.org/hg/mutt/raw-file/tip/doc/devel-notes.txt]

When preparing/maintaining 3rd patches, see:

  * [http://dev.mutt.org/hg/mutt/raw-file/tip/doc/applying-patches.txt]
  * [http://dev.mutt.org/hg/mutt/raw-file/tip/doc/patch-notes.txt]
  * [wiki:PatchList]

== Brainstorming ==

This lists topics that we're currently collecting ideas for:

  * NewMailHandling overhaul
  * UnifyMailboxInterface (more issues than only new mail handling)
  * MailboxDriverCleanup and MAPI support