• View
• Edit
• History
• Print

GoogleCodeIssueTracker

Bug tracker

We have started using the issue tracker from Google Code. I have setup url redirection, so http://bugs.solfege.org redirects to http://code.google.com/p/solfege/ and http://bugs.solfege.org/bug-number redirects to the correct page at google. Example: http://bugs.solfege.org/2

This page tries to describe how we use the bug trackers, and how the different labels are interpreted. This is not the final way to do it. Suggestions are welcome, either here or on the mailing list.

Bug status values

Open bugs:

New

Issue has not had initial review yet

Accepted

Problem reproduced / Need acknowledged

Started

Work on this issue has begun

Closed bugs:

Fixed

The bug has been fixed in a released version of Solfege

FixedNotReleased

Fixed in the bzr repo, not released yet

Invalid

This was not a valid issue report

Duplicate

This report duplicates an existing issue

WontFix

We decided to not take action on this issue

Labels

Music

This bug has work that musicians with no programmer skills can do. You don't even have to write lesson files.

Lilypond uses labels to say which release fixed a bug.