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.
In that case QA should step in! every bug has a QA member, we have to ask them ehat is the problem, how can we help to move forward, should we change some process or what is their opinion?
I don't think anybody will report any more bugs if they experience this behaviour once.
agree another thing what I don't like, when assignee route me to the upstream. If I am a user and use openSUSE and report a bug, I don't want to go anywhere else to create an issue in another bugzilla. Maintainer should care about my reported issue through upstream and back to the distribution.
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.
Maybe someone in that list could answer for that questions...
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.
I agree. But we should clarify this is for just for kick-off and we will never ever do it again.
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.
QA should care about it. Maybe we have to create a list about the positions/maintainers/roles which is not assigned to anyone. best k -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-project+help@opensuse.org