Re: bug perception

----- Original Message ----- From: "waldschrott" <waldschrott@kiffen.de> > a) we (php-qa) seem to have missed a few bug reports, I´m just browsing > through all open reports and a few ones aren´t touched yet, I think we > can reduce these 380 to at least 250-300 again checking the whole stuff > again. I am sure that we did miss, misinterprete or not comprehend a significant number of bug reports. I have been playing a bit of catch up over the last few days and have not really been on top of the bugs. I am going to try to go through the process that I described several messages ago to try and organize the bugs. As soon as this is done, I will start on modifying the bug tracking system. I will see if Sascha or someone else with admin priveledges can make a copy of the bug database for me to play around with so that I don't accidentally mangle the live data. I will also go through and test the items that I have assigned to myself as soon as I can get apache running in my win2k system. > b) there are "old"+"outdated" reports with the state "analyzed" > or > "assigned" noone took care of. We´ve to browse through them too. As I proposed in a previous message: 1.) Remove or update old feedback status bugs 2.) Ensure that bugs are in appropriate categories 3.) Find the duplicate bugs Once we have done this, it should be much easier to: 1.) Group into packages based on related problem 2.) Group bugs within packages by OS 3.) Try to validate the bug 4.) Try to find developers who can work on the fixes > What sense does a "assigned to..." value make if the person it is > assigned too doesn´t care? We should add a reminder to the bug system > which reminds the existance of an assigned bug once a week... I am not sure how to handle this - a reminder would not be a terrible thing. If someone starts to get too irritated by the nagging, they can always change the bug status. Zak