FIXED - the bug has been fixed or the feature has been implemented.If a bug stays "stuck" in some unresolved state for a long time, it may eventually be resolved as WONTFIX or ARCHIVED. Issues in the NEED_EXAMPLE and TESTING states will be marked RESOLVED if there is no further activity. RESOLVED - closed, issue has been fixed or rejected.TESTING - the submitter should test the fix NEED_EXAMPLE - more information is required from the submitter CONFIRMED - a maintainer believes the report is valid, and the issue is under discussion.UNCONFIRMED - no one has yet triaged the report.If you're using Windows, anything unusual about your setup, including but not limited to:Īs a bug is tracked, it will go through various states, some of which will demand your attention:.The precise traceback or error message you received.Whether what you're doing used to work before upgrading (this triggers special attention).Helpful Information to include in your description wish - low priority (most feature requests end up in this state)Ī regression is defined as a bug that breaks something that used to work in earlier releases.Ĭritical bugs may trigger out-of-cycle releases.Ĥ.2.normal - medium priority (no data loss involved).urgent - high priority (bug that's blocking development or is a regression).
#TORTOISEHG BUGS SOFTWARE#
#TORTOISEHG BUGS HOW TO#
See ContributingChanges for how to send a patch we'll love.īefore filing a new bug, please use the search form to try to locate similar bugs. Since we'll never run out of patches submitted the right way that are much easier for us to deal with, your patch will go unloved. all of our tooling and automation for patches is aimed at email.Most bug tracker usage will need you to register an account so that you can get updates on your bug reports. It's used for tracking known bugs, requested features, and wishlist items. Mercurial's bug tracking system is located at. Please first check if your issue is caused by a GUI tool or third-party extension.