|
Size: 2484
Comment:
|
Size: 2719
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 7: | Line 7: |
== Finding the right bug tracker == Bugs are often caused by a GUI tool or extension. If you believe this to be the case, its best to report the bug there first. * [[http://bitbucket.org/tortoisehg/stable/issues|TortoiseHg]] |
Bug Tracker
Using the Mercurial bug tracker.
Contents
1. Finding the right bug tracker
Bugs are often caused by a GUI tool or extension. If you believe this to be the case, its best to report the bug there first.
2. Getting started
Mercurial's bug tracking system is located at http://mercurial.selenic.com/bts. 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.
To create a new issue, click "Create New" under "Issues" in the sidebar. Put a specific summary of your issue in the title.
3.1. Choosing a priority
Please try to select the most appropriate priority:
- critical - data loss or security issue
- urgent - bug that's blocking development or is a regression
- bug - bug that's not blocking development
- feature - it's not a bug, it's a feature
- wish - would be nice
(A regression is defined as a bug that breaks something that worked in earlier releases.)
3.2. Information it's often helpful 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
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
- in-progress - a fix is being developed
testing - the submitter should test the fix
- resolved - issue is solved
- done-cbb - issue is not going to be fixed
Issues in the need-eg and testing states will get marked resolved if there is no further activity.
Don't comment on a resolved bug, it will reset the state to chatting!
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
See ManagingBugs for the developer side of the process.