-
Notifications
You must be signed in to change notification settings - Fork 0
Issue Tracker
Paul Bunyan edited this page Jun 19, 2014
·
1 revision
This page outlines the rules for posting issues in the issue tracker.
This should be implied, but the issue must be relevant to the project. Spamming of the issue tracker is not permitted.
It is also requested that conversations in the issue tracker remain polite. They should remain focused on the issue and should not degrade into a flame war.
When posting an issue described below, always label the issue with the appropriate label.
- Be specific. Describe your system, exactly what the bug does, and the steps to reproduce the bug.
- If you can identify the problem as OS-specific, then apply the proper label that describes your OS. Do not apply a label if you do not suspect that the problem is OS-specific. If, after research, the problem is OS-specific, the label will be added then.
- If the issue is with a specific part of this project, apply the label that describes that component of iash.
- If you are a collaborator:
- Assign the issue to the collaborator best able to address the issue.
- If you are assigned an issue, then research the bug and try to reproduce it on multiple systems. Post your findings to the issue tracker.
- Mark an issue confirmed only when you are reasonably certain that the bug is a real bug and not an isolated incident.
- If it is an isolated incident, research related aspects of the library to see if there as a more general root cause. If you find that there is a bug that causes this issue to occur, open a new issue, comment on the old one about your findings and link the new issue, then close the old issue.
- Before posting a question, check the wiki to see if it provides your answer.
- Please be clear and specific. We will be unable to help you if you are using vague and confusing language.
- When posting an enhancement, please describe what you want to add to the best of your ability.
- When posting an enhancement, ensure that the enhancement would add value to the library.
- If the question/enhancement is OS-specific, apply the according label. DO NOT apply an OS-specific label if it does not have to do specifically with an OS.
- If you are a collaborator (Enhancements only):
- Check to see if the enhancement is viable.
- If it is, mark the question as "Confirmed"
- If not, label the question "wontfix" and set the according milestone.
- When an enhancement is confirmed, assign the issue to a collaborator who is best able to address the issue.
- Check to see if the enhancement is viable.
iash wiki -- Go home
-
Current version
- API reference
- Runtime documentation
-
Older versions
- API reference
- Runtime documentation
- Posting to the Issue Tracker