Many times, a new user of D (and even some experienced ones) will post a
bug to bugzilla with not enough or just enough information, but could be
way more informative.
For example, take http://d.puremagic.com/issues/show_bug.cgi?id=6323
I have to download this code and compile it, to see what he is talking
about (no error messages or explanation of what's wrong). (sorry to pick
on this bug, it's not the only one, but the most recent)
I think requiring someone to download code and compile it is way too much
overhead to determine whether a bug is trivial, duplicate, invalid, etc.
In other bug reporting systems I've used, when you create a new bug, it
gives you a template to fill out (i.e. steps to reproduce, any relevant
error messages). I think this would go a long way to getting more
informative bug reports.
Is it possible to add something like this to D's bugzilla? Do other
people think this is a good idea?
I'll give a sample:
-------------------------------------
Please answer the following mandatory questions
1. List an example that causes the bug (please reduce as much as
possible). Do not paste more than 100 lines of code.
2. If relevant, list the command line used to compile, including any flags
passed to the compiler
3. If any errors are output by the compiler, list them here
4. What is your expected result?
5. What is the actual result?
Note: please use the selectors above to fill out as much detailed
information as possible (OS, architecture, version of D, etc.)
-------------------------------------
I'm not stuck on this form, probably the most prolific bug fixers could
come up with a better one.
-Steve
