o New: this is how user reported bugs come in to the list. o NeedInfo: set if the report does not have enough info to decide if it is our bug. The comment should include the info needed from the reporter. o Triaged: set after we read the bug report and decided it is our bug. Add tags for version that has the bug, probable module, and one of the Test flags. o Started: set to let others know you are actively working on this problem. (Optional) o Commit: a fixed is committed to SVN. The comment should include the revision number of the commit (so we can look up regressions) and the next expected release version (so reporters know the fix is not out until that release). The committer should set "Owner" to themselves. o Fixed: when the release is created, all bugs with Commit are marked Fixed and the release version number is put in the comment. Please copy the issue number and title when your commit fixes a bug, this is used to create the change log. o Verified: when the original poster reports that they tried the fix and it works. A courtesy/thank you for the reporter. o ProbablyWorks: an old bug report which was probably fixed but which we did not take direct action to fix. o InsufficientInfo: an old bug report with requests for user info that never appeared. o UserResolved: reporting user has a solution and we did not fix it. o OtherComponent: we have strong reasons to believe that this problem is not one we can fix in Firebug. o Duplicate: we think we have another bug report on the same subject. Please add a comment encouraging the user to check: a surprising number of times the bugs are not in fact duplicates.
Tickets normally follow this path: o New - New ticket o Triaged - Ticket has been read and categorized o Started - Somebody is actively working on the ticket o Commit - Problem is fixed and code committed to the source repository o Fixed - Released version has fixed, user should verify o Verified - User has verified that this works - Mike Ratcliffe On Feb 22, 10:37 am, woomla <[email protected]> wrote: > Hi, > > I was hoping to find some documentation about the issue statuses. And > in particular the actions the firebug team will take on them and what > is they expected from the op. > > I.e. If the status of my issus is fixed or commit or verified, what > actions do you want from me. > And if the status is Triaged, what will you do with that issue. > > I think you guys (no gals?) do a hell of a great job here. So I'm not > looking for some legal commitment or something stupid like that. All I > want to know is what could be expected from you. And off course from > me so I can participate more meaningful. > > Maybe a nice wiki page? > > Woomla -- You received this message because you are subscribed to the Google Groups "Firebug" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/firebug?hl=en.
