I'm going to bulk-edit all these bugs to close them. Yes, it's very poor QA practice, but we don't really seem capable of doing much better at this stage in development.
Salut,
Jordi.
Jordi Salvat i Alabart wrote:
Hello. I'm just back from my vacation.
I see 1.8.1 was released. I think we should verify all bugs reportedly fixed by that release are actually resolved and CLOSE them. I've made a search:
http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfield=bug_status&chfieldfrom=01%2F01%2F1970&chfieldto=01%2F02%2F2003&chfieldvalue=&product=JMeter&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=JMeter-RESOLVED&newqueryname=&order=Reuse+same+sort+as+last+time
But the count is only 23,... I guess my search is wrong, or maybe many were marked as RESOLVED *after* the 1.8.1 build. We should probably review the whole list:
http://nagoya.apache.org/bugzilla/buglist.cgi?bug_status=RESOLVED&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&bugidtype=include&bug_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&product=JMeter&short_desc=&short_desc_type=allwordssubstr&long_desc=&long_desc_type=allwordssubstr&bug_file_loc=&bug_file_loc_type=allwordssubstr&keywords=&keywords_type=anywords&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&namedcmd=JMeter-RESOLVED&newqueryname=&order=Reuse+same+sort+as+last+time
(the count is 57 here).
Please have a quick look and close those you positively know are resolved (because you've tried and they don't happen, not just because you fixed them).
Question: would it be a good idea to refrain from closing bugs you've fixed yourself?
Pro: independent verification will certainly ensure better quality.
Con: demands more work from the team, since TWO people (fixer and verifier) must understand the bug and verify the fix.
Proposal: on the next release, we should consider going through this task before actually releasing. Yes, it's a pain, but I think it's necessary to ensure reasonable quality.
Salut,
Jordi.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
