Differences between revisions 23 and 24
Revision 23 as of 2011-01-07 01:23:40
Size: 3239
Comment: explain need-eg and done-cbb
Revision 24 as of 2011-01-09 16:41:36
Size: 3215
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Line 9: Line 8:
Line 18: Line 16:

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.
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.
Line 25: Line 21:
Line 31: Line 26:
Line 38: Line 32:
 * wish - would be nice   * wish - would be nice
Line 43: Line 37:
Line 50: Line 43:
  * Virtual Box
   * CygWin
  * using network shares
  * using an on-access virus scanner
  * !VirtualBox
  * !CygWin
  * using network shares
  * using an on-access virus scanner
Line 56: Line 49:
Line 72: Line 64:
Line 77: Line 68:
 * don't attach patches to the wiki, see ContributingChanges instead   * don't attach patches to the wiki, see ContributingChanges instead
Line 80: Line 71:

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://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. 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 (eg = example)

  • 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 (cbb = could be better)

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

6. See also


CategoryBugs CategoryProject

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