-
Notifications
You must be signed in to change notification settings - Fork 0
Issue Tracker guidelines
This page describe how the issue tracker for GDG-Connect is organised.
Every issue is assigned one or more tags, not only to to make them easier to find, but more importantly to indicate their status.
Assigned to issues that describe bugs. Bug are critical if they affect a core functionality of the app. Bugs are minor if they do not prevent the user from using any functionality, but can still be annoying.
When a feature request is accepted, that is, it is considered a good fit for the app, the issue receives a blue tag, which further specifies what kind of enhancement it contains. A new feature is an enhancement that adds a completely new functionality to the app. A small-enhancement improves an existing functionality. Besides functional enhancements, there are also tags for non-functional enhancements, such as documentation, performance or robustness.
Assigned to explain either the lack of progress on certain issues, or why was it closed without getting fixed. The issue is duplicate if it has been reported before. The issue is invalid if it describes a problem that does not actually exist, or is caused by external factors. The issue needs-info if more feedback from the user is necessary for its resolution. The issue is wont-fix if the developers acknowledge that it is valid, but decide not to implement it, for whatever reason.
Indicates if the issue has high, medium or low priority. This serves only as a guideline or suggestion. Since everyone is doing volunteer work, they are free to work on whatever issue they find most interesting, regardless of the priority.
Assigned to issues that contain questions or discussions, not necessarily bugs. Feature requests receive this tag until the developers decide whether to accept it (give it a blue tag) or reject it as wont-fix.
Assigned to issues that are easier for newcomers to fix.