Bug Tracker

Using the Mercurial bug tracker.

1. Finding the right bug tracker

Please first check if your issue is caused by a GUI tool or third-party extension. Other bug trackers include:

2. Getting started

Mercurial's bug tracking system is located at http://bz.selenic.com/. It's used for tracking known bugs, requested features, and wishlist items.

Most bug tracker usage will need you to register an account so that you can get updates on your bug reports.

3. Creating a new issue

<!> Before filing a new bug, please use the search form to try to locate similar bugs.

When creating a new issue, put a specific summary of your issue in the title.

3.1. Choosing a priority

Please try to select the most appropriate severity:

Once the bug is filed, there will be a priority associated with it:

(A regression is defined as a bug that breaks something that worked in earlier releases.)

3.2. Helpful Information to include in your description

4. The life cycle of a bug

As a bug is tracked, it will go through various states, some of which will demand your attention:

Issues in the NEED_EXAMPLE and TESTING states will be marked RESOLVED if there is no further activity. If a bug stays "stuck" in some unresolved state for a long time, it may eventually be resolved as WONTFIX.

Resolutions - how a bug is closed out:

5. Etiquette

6. See also


CategoryBugs CategoryProject