https://bugzilla.novell.com/show_bug.cgi?id=623286
https://bugzilla.novell.com/show_bug.cgi?id=623286#c28
Nick Couchman
(In reply to comment #26)
Well, I stand corrected. Go ahead and close the ticket even though it has not been resolved.
I don't see that anyone internal is suggesting to close this bug. It has been reassigned to appropriate component for fixing.
So, I understand the point about this being a community project, and that you rely on the community to fix some of the bugs. I also realize that I'm not a huge contributor in terms of code (and you would probably thank me for that if you knew my low level of programming skills :-). That said, this last comment was over two weeks ago, openSuSE 11.3 has been out for five or six weeks, and the fix for this issue has been known/available in the KOTD and OBS Kernel repositories for three to four weeks. So, the question is: why hasn't this shown up in the form of a kernel update in the openSuSE 11.3 repositories?? I'm not trying to be impatient - I'm happy to use the OBS Kernel repo or KOTD, and I very much appreciate the folks who can and do donate their time and energy to developing openSuSE, but this is a pretty major issue in a release of a Linux distribution that is considered "stable." I understand your point about the community development of this project, but if you expect folks to use openSuSE as a distribution (and, consequently, move into SLES for Enterprise-level functionality), these issues need to be responded to quickly, and four weeks for a problem of this magnitude is anything but quick. Issues like this will reflect on the entire "SUSE" product line, and that includes the Enterprise products. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.