Hey Guys
I am not asking if the site or server is down. What I am asking is the concept broken?
In FC4 and FC5 days one could report a bug and get a response. While it was true that I did not always like or agree with the response, I did get one. With F7 it seems(at least to me) that if you do not get a response within a week, you will never get a response. I have posted several bugs in F7 that got responses and solutions within a week, these are the almost trivial bugs(I still appreciate the time spent by those packagers that helped me). All of the serious bugs I have posted have gone without response. Over the last few months I have posted more information to these bugs as updates have come out, still no response. If more information is needed fine, post that more information is needed. If it is a duplicate, then post that it is a duplicate. But just allowing the bug to sit there ignored is just wrong.
I do not know if it is a situation where the talent has been reassigned to work on F8, if it is the shear number of bugs in F7, a combination of the two, or some other combination of factors. It also seems to me that the types of bugs are different in F7 than in previous versions. F7 errors (at least mine) do not seem to keep the system from running, they just seem to keep the system from running properly. One example of this is that within system disk transfers are much slower in F7 than they were in FC6 or FC5 (8-40% depending on system). The hdparm tests are the same but " time cp" test show considerable reduction in transfer speed. Yet there is no response to the bug in bugzilla. For those of us that move 10gig data sets around several times an hour this is a significant bug.
I posted this basic question to the new Ask Fedora section. Their basic response was to go to the dev lists. Well if I have to go to the dev lists to get a bug fixed, what is the point of bugzilla?
Thanks
Lazlow


Reply With Quote
cryptic error messages,
and mysteriously disappearing/reappearing hardware, it's almost a relief to reboot into FC6, and watch the familiar "XError: BadMatch..." warning messages scroll by at a rapid clip in ~/.xsession-errors, on an otherwise functional operating system.
