![]() |
Blaze
3.6
|
One of the most important aspects of the Blaze project is the issue management on the official Blaze Bitbucket page. We cordially invite all Blaze users to submit feature requests and bug reports, as we believe that this is a significant part of making Blaze a better library. However, we are asking to follow a small set of guidelines when creating an issue to facilitate the issue management on our side and also to make issues more useful for users of Blaze.
The title is the most important detail of an issue. A well chosen title makes it easy to grasp the idea of an issue and improves the discoverability. Therefore, please choose a title that is ...
Also, please create a separate issue for each idea/problem/etc. A very general title or an "and" in the title could be an indication that the issue is not specific enough and should be split into several issues.
The description should help us to understand your idea or problem in as much detail as possible. Also, it helps to clearly spell out your expectations (how a feature is supposed to work, how the behavior should be, etc.). Please spend a couple of minutes to try to make the description as comprehensive as possible.
There is no need to assign the issue to a particular person. It is perfectly ok if you just ignore this setting.
There are four kinds of issues available in the Bitbucket issue tracker: Bug, Enhancement, Proposal, and Task. In the following we try to give guidelines on which kind to choose for a particular issue:
Please choose the category Bug if ...
Please don't choose the category Bug if ...
If you select the category Bug, please also try to provide a minimum example that fails. That helps us to minimize the time to resolve the bug.
As we try to keep Blaze bug-free, we will always prioritize bug issues. However, we will also quickly close bug issues as "wontfix" if the described issue is not a bug (i.e. one of the problems mentioned above). We will not relabel a bug issue to Enhancement or Proposal, even if they would be reasonable extensions to Blaze.
Please choose the category Enhancement if ...
Enhancement is very similar to Proposal, so we don't mind if an Enhancement is labeled as a Proposal or vice versa. Just make sure you don't request an extension or new feature as a Bug.
Please choose the category Proposal if ...
Proposal is very similar to Enhancement, so we don't mind if a Proposal is labeled as an Enhancement or vice versa. Just make sure you don't request an extension or new feature as a Bug.
Please choose the category Task if ...
Via the priority of an issue you can tell us how important the issue is to you. Therefore the priority can have an influence on when we will deal with the issue. However, unfortunately we don't have an infinite amount of time and we can not deal with an arbitrary amount of issues at the same time. We will therefore take the priority into account, but mainly schedule the issues based on impact to all Blaze users and the estimated time to resolve it.
You can choose between Blocker, Critical, Major, Minor, and Trivial.
Please choose a Blocker priority if ...
Please note that the categories Enhancement or Proposal should never be a Blocker!
Please choose a Critical priority if ...
Please choose a Major priority if ...
The Major category is the default setting in Bitbucket and we therefore consider it as the default priority for issues.
Please choose a Minor priority if ...
Please choose a Trivial priority if ...
You can always provide us with additional information in the form of attachments. Feel free to attach something to the issue if ...
We appreciate anything that simplifies our work and speeds up our progress.
Previous: Frequently Asked Questions (FAQ) Next: Blaze References