Skip to content
xizhao edited this page Nov 21, 2014 · 1 revision

FOSSology has recently switched to using GitHub's issue tracker to track bugs. All bugs and enhancements need to be entered so that we don't lose track of them, can prioritize, assign, and so code fixes can refer to the bug number in its check-in comments. The bug report usually contains much more detail (including test cases) than can be reasonably put in check-in comments, so being able to correlate the two is important.

General Guidelines

There is a page to general guidelines for entering a new bug. If you haven't read it you should. It's a quick read and will help you write good bug reports.

For more information re: issue tracking, see the Help page for Redmine.

Field Details

Most of the fields are self-explanatory; however I'd like to emphasize a few.

Target Version

This is pretty important for setting priorities. Leave it blank if you do not know the answer.

Description and Attachment

I would like to reiterate how critical these are to have enough information to understand and reproduce the bug or understand an enhancement request.

Bug Assignment

After the bug is created it will have a status of "NEW" and an email will be sent to the responsible developer. That developer needs to either accept the bug or reassign it to someone else. If someone else wants to take a bug assigned to you, they need to contact you first. This way we don't have multiple people working on the same thing without knowing what the bug owner is doing.

Resolution

When you fix a bug (or implement an enhancement), add your comments and change the status to "RESOLVED".

The Bug Police

The bug police will get you if: * If you don't refer to a bug number when you check in a fix. * If you leave a bug in the "New" state for very long. * If you don't close a resolved bug. * If you discover a bug and don't file a bug report. See exceptions. * If you close a bug before the problem is actually fixed in SVN.

Exceptions

In the following cases, you don't need to file a bug report: * You discover a bug (or make an enhancement) in your own code and the time between discovery and checkin is less than a few hours.

Clone this wiki locally