Differences between revisions 1 and 30 (spanning 29 versions)
Revision 1 as of 2005-10-20 19:58:48
Size: 337
Editor: mpm
Comment:
Revision 30 as of 2012-05-12 17:03:09
Size: 3417
Editor: JohnHein
Comment: fix instructions for reporting new bugs
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
{{{ #pragma section-numbers 2
= Bug Tracker =
Using the Mercurial bug tracker.
Line 3: Line 5:
                    language db ui email hooks comments
bugzilla perl mysql
roundup python sqlite?
request-tracker perl mysql/pg
mantis php mysql
debbugs perl none
jitterbug c none
<<TableOfContents>>
Line 11: Line 7:
== 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:
Line 12: Line 10:
 * [[http://bitbucket.org/tortoisehg/thg/issues|TortoiseHg 2.x]] ~-([[http://bitbucket.org/tortoisehg/stable/issues|1.x series]])-~
 * [[http://bitbucket.org/durin42/hgsubversion/issues|hgsubversion]]
 * [[http://github.com/schacon/hg-git/issues|hg-git]]
 * [[http://javaforge.com/project/HGE/tracker|Mercurial Eclipse]]
Line 13: Line 15:
}}} == 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 [[http://bz.selenic.com/createaccount.cgi|register]] an account so that you can get updates on your bug reports.

== Creating a new issue ==
<!> Before filing a new bug, please use the [[http://bz.selenic.com/query.cgi|search form]] to try to locate similar bugs.

When creating a [[http://bz.selenic.com/enter_bug.cgi?product=Mercurial|new issue]], put a ''specific'' summary of your issue in the title.

=== Choosing a priority ===
Please try to select the most appropriate priority:

 * critical - top priority (data loss or security issue)
 * urgent - high priority (bug that's blocking development or is a regression)
 * bug - normal priority (bug that's not blocking development)
 * feature - eventually (it's not a bug, it's a feature request, good patches will probably be accepted)
 * wish - very low priority (it could perhaps be nice to have but is close to a done-cbb resolution)

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

=== Helpful Information to include in your description ===
 * The version of Mercurial you're using
 * The operating system you're using
 * Any third-party tools you're using
 * The command you were running
 * The precise traceback or error message you received
 * If you're using Windows, anything unusual about your setup, including but not limited to:
  * !VirtualBox
  * !CygWin
  * using network shares
  * using an on-access virus scanner

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

 * unread - no one has yet responded
 * chatting - issue is under discussion
 * need-eg - '''more information is required from the submitter''' (e.g.: abbr. of Latin ''exempli gratia'')
 * in-progress - a fix is being developed
 * testing - '''the submitter should test the fix'''
 * resolved - closed, issue is solved
 * done-cbb - closed, issue is not going to be fixed (cbb = could be better / can't be bothered)

Issues in the need-eg and testing states will get marked resolved if there is no further activity.

== Etiquette ==
 * be responsive - developers are very busy
 * try to answer the specific questions asked by developers
 * paste tracebacks into message fields rather than uploading attachments
 * test fixes!
 * don't attach patches to the wiki, see ContributingChanges instead

== See also ==
 * ManagingBugs for the developer side of the process
 * [[IRC]] for real-time diagnosis and support
 * Our [[MailingLists|mailing lists]] for general discussion

----
CategoryBugs CategoryProject

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 priority:

  • critical - top priority (data loss or security issue)
  • urgent - high priority (bug that's blocking development or is a regression)
  • bug - normal priority (bug that's not blocking development)
  • feature - eventually (it's not a bug, it's a feature request, good patches will probably be accepted)
  • wish - very low priority (it could perhaps be nice to have but is close to a done-cbb resolution)

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

3.2. Helpful Information to include in your description

  • The version of Mercurial you're using
  • The operating system you're using
  • Any third-party tools you're using
  • The command you were running
  • The precise traceback or error message you received
  • If you're using Windows, anything unusual about your setup, including but not limited to:
    • VirtualBox

    • CygWin

    • using network shares
    • using an on-access virus scanner

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:

  • unread - no one has yet responded
  • chatting - issue is under discussion
  • need-eg - more information is required from the submitter (e.g.: abbr. of Latin exempli gratia)

  • in-progress - a fix is being developed
  • testing - the submitter should test the fix

  • resolved - closed, issue is solved
  • done-cbb - closed, issue is not going to be fixed (cbb = could be better / can't be bothered)

Issues in the need-eg and testing states will get marked resolved if there is no further activity.

5. Etiquette

  • be responsive - developers are very busy
  • try to answer the specific questions asked by developers
  • paste tracebacks into message fields rather than uploading attachments
  • test fixes!
  • don't attach patches to the wiki, see ContributingChanges instead

6. See also


CategoryBugs CategoryProject

BugTracker (last edited 2020-01-16 06:00:32 by aayjaychan)