Hi, 2010/11/4 Marcel de Rooy <M.de.Rooy@rijksmuseum.nl>:
Couldn’t find this on the wiki. Should I leave a bug on resolved/fixed, resolved/invalid etc. or should they always go to closed in the end?
Just some number: resolved+fixed=2636 bugs. Closed/fixed= only 78.
See http://bugs.koha-community.org/bugzilla3/page.cgi?id=fields.html#status for an explanation of Bugzilla's recommend use of the status field. In principle, once a bug has been marked as resolved (i.e., that a fix has been pushed to the master or appropriate maintenance branch in the public repository), the next step would be for somebody such as the original submitter or a QA volunteer to verify the fix and mark the bug either verified or reopened. A bug wouldn't be marked closed until the fix was available in a packaged release. This is a good idea, actually, but for it to work, there would need to be more people actively wrangling bugs than seem to be available at the moment. So in practice, a RESOLVED FIXED should be considered equivalent to a VERIFIED/CLOSED FIXED, but if anybody wants to take the additional step of verifying bugfixes and marking them as closed after a release, doing so would be a goodness. Regards, Galen -- Galen Charlton gmcharlt@gmail.com