On 11/13/2010 07:39 AM, Kálmán Kéménczy wrote:
Hi there,
2) Assigned entries, even though they are P1, even though there are patches with fixes attached, are not taken care of. There is 1572 of all opensuse bugs which are left for more than 400 days without any attention. Many of them are not even reassigned to proper maintainers.
We have to assign them to the current maintainers and they should evaluate them during the next hack week or bugzilla clean week or so,
The Fedora way is not friendly at all. If the maintainer could not decide the state of the issue, they could change product version to current or developer release and set to "needinfo" for the reporter and/or add them as Junior Jobs bug for reproduce or evaluate for the current stable or development release.
Ok, but note that there are bncs that are not changed/fixed even though there is enough of data (patches, great debug info provided etc.). The bugs are not fixed and closed though. That falls exactly to the case 2). It looks like "we asked you for some info and we don't care anymore". Many of bugs I reported ended up in this state. Examples are broken intel graphics since 11.3 (but I'm at least reminded to test the latest release every 2 months or so), reported bug in nmap with exact line number and described error. The same for libacl. Vim parses the gcc output wrong since we use gcc 4.5 and many others. The last four are fixable in an hour, but the assigned people don't care for years. I'm not counting gnome bugs which are assigned for years to gnome screening team and are not touched at all by anybody. I don't think anybody will report any more bugs if they experience this behaviour once. Another thing is that we have reports from milestones and RCs, but we go through them after we release GA. What are the testing releases good for if we don't even try to fix the reported issues? (I fixed many such kernel bncs for 11.3 RCs recently.) Some once-a-year happening like whatever-week won't improve this at all. Some constructive comments. I still think we should close bugs which are a) untouched for years AND b) are against unmaintained codebases. It should be noted there, that we are closing it because it is unsupported product and if the bugs still persist in later releases, we want reporters to reopen. Otherwise we will have thousands of rotten entries. Further we need people who will regularly assign bugs to proper developers/maintainers. This is not easy. I personally have problems to guess the correct person. I use osc maintainer, osc log, dig info out of osc metas and internal novell wiki (kernel maintainers are specified there for kernel components). It would be great if there was one reliable method/tool. As none of those above returns the proper person and bugs happen to be without progress. It it also because some assignees don't care. No, they should be forced to reassign appropriately (or reassign back to screening lists) if they know nothing about the package. regards, -- js suse labs -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org