Bug status clarifications requested

Paul Dufresne dufresnep at gmail.com
Thu Nov 22 17:21:30 UTC 2007


Often while triaging bugs, I come on bugs that were reported on old
versions, but seems to be fixed in current or development version.
That said, most of the time I have no idea exactly when, or where it
has been fixed. I use to mark them Invalid in this case, because I
take that 'Fix release' should only be use by a developer to mark that
his patch not only have been committed, but released.

But then reading
https://wiki.ubuntu.com/Bugs/Responses#head-246b9a0b2091d7aee70afd2b0579dbbc986eb51b
I begin to seriously think I should mark them 'Fix released'.

An other less common situation I wonder if I should use 'Fix released'
or not is in:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/21995
Here the bug have been fix in Debian, but the version in Hardy is not
yet the same as the fix one in Debian.

Last, I often confirm bugs that I am not sure it is a bug because I
have not enough knowledge of the package, but I am pretty sure the
package maintainer would have no problem with the information given up
to now. I just hope it is right to do so.

Also, I believe the package naming scheme is supposed to indicate if
the package is specific to Ubuntu, taken from Debian, taken from an
other project. But I don't easily find back where this is explained.

Finally, I'd like to say that bug status is like documented in too many places:
https://wiki.ubuntu.com/Bugs/CommonTasks
https://wiki.ubuntu.com/Bugs/Status
https://wiki.ubuntu.com/PackagingGuide/Lists/BugStatus (Rejected
should become Invalid here)
https://wiki.ubuntu.com/PackagingGuide/Bugs




More information about the Ubuntu-bugsquad mailing list