Finding, Filing and Following Bugs (aka Issues)

[marxistvegan]

I am not a developer, but I have been following the development of QSB
and noticed a number of things that would be nice to generalize for
new comers when it comes to Finding, Filing and Following Bugs, which
are known hereafter as Issues (Bugs = Issues).

IF You Find a Issue:
First, Search The Issues List to See if it Exists:
http://code.google.com/p/qsb-mac/issues/list

Second, If The Issue Does Not Exist:
File a new one, but read up on how to file one first:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
details are important, so go step by step to create the bug that you
are filing.

IF You Find an Issue You Want to Follow:
Instead of Commenting you support for the bug, Click the "Star" this
will allow you to receive updates to the bug as it is processed.

IF You Are Not Sure If You Found An Issue Search Here in the General
Discussions to see if someone else mentioned it:
http://groups.google.com/group/qsb-mac-discuss

These are some helpful tips that I think will help the development
team. I'll admit I did not follow these when I first started looking
at QSB, but I began to see over time the advantage it is to the
project development and I think it really helps with communication
between developers and followers/testers.

Hope this is helpful to everyone. :)

[marxistvegan]

One addition to this would be

One Issue Per Issue, I think it is easier instead of developers
merging Issues together.

Can someone sticky this post?

Stephen