|
Size: 4070
Comment: spam
|
Size: 0
Comment: Spam wikipage deleted by robot
|
| 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. <<TableOfContents>> == 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: * [[http://javaforge.com/project/HGE/tracker|Mercurial Eclipse]] * [[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]] == 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 severity: * bug - the software isn't working as you expect * feature - it's not a bug, it's a feature request, good patches will probably be accepted Once the bug is filed, there will be a priority associated with it: * critical - top priority (data loss, security issue, or major regression) * urgent - high priority (bug that's blocking development or is a regression) * normal - medium priority (no data loss involved) * wish - very low priority (it could perhaps be nice to have but may be close to a WONTFIX resolution) {i} A regression is defined as a bug that breaks something that worked in earlier releases. {i} Critical bugs may trigger out-of-cycle 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: * UNCONFIRMED - no one has yet triaged the report * CONFIRMED - a maintainer believes the report is valid, and the issue is under discussion * NEED_EXAMPLE - '''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 has been fixed or rejected 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: * FIXED - the bug has been fixed or the feature has been implemented * INVALID - the issue was rejected * WONTFIX - the issue might have been valid but will not be addressed, or has stayed unresolved for too long * DUPLICATE - a pre-existing issue covers the same topic * WORKSFORME - the issue could not be reproduced == 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 BTS, 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 |
