Re: Older QC reports

"Patrick Moloney" <NewsID*at*SandrockSoftware.c*o*m> wrote in message news:47425b72$1@xxxxxxxxxxxxxxxxxxxxxxxxx

The main point of my post was that the effect of QC has become negative
rather than positive for many users. If you can't see that just try
reading this thread again. It's about expectations. Mine have changed
vis-a-vis QC. I still submit a posting when I feel there is something
that should be addressed, but it's a one-way contribution. I see it as
information for CG, rather than something I'm hoping and waiting for a
fix or even a response. I have to try to remember to go back and
check, just in case someone asked for more information. But I don't
check out of any expectation any more. I used to do that. I've
accepted what it is - at least as I see it. But I don't think it's
getting the response in the customer community that CG and apparently
some here believe it is, or expect it is.


While I don't doubt that there are at least some number of users that feel similar to you, I *do* doubt it is anything near a majority or even a *significant* minority. This is not a criticism per se, you have to judge it by what you see (and don't see). All I can say is that I don't understand that perception.

Before there was QC there was... nothing. We customers rightly complained for years about Borland being ridiculous about their aversion to admitting the existence of bugs (on the basis that any such admission would hurt sales).

But if one is going to have a public bug tracking system, and if it is going to be an *honest* system, then by definition there are going to end up being some number of items that do not get the attention that some believe they deserve. If you were satisfied with the specific bugs that have been resolved, chances are someone else would not be, and vice versa (i.e. old story: cannot satisfy everyone).

Hopefully CG will continue to grow and be able to dedicate more resources over time, but no matter what, resources are always going to be limited and it is not possible to address every reported bug in any given amount of time, and in some cases some bugs are going to slip through the cracks seemingly forever. We can argue over the merits and severity of any given bug, but only so many bugs can be handled in so much time.

A simple look at QC statistics shows an *enormous* number of bugs reported via QC have been resolved over the last several releases since QC was introoduced, and the numbers increase with every release (hopefully reaching a point where they begin to decrease - reporting rate of new bugs dropping below their ability to address them).

Seeing the existence of any number of unaddressed bugs while ignoring all the good that has been accomplished as a result of QC is kind of self-defeating IMHO.

--
Wayne Niddery - Winwright, Inc. (www.winwright.ca)

.

Relevant Pages

  • Re: [opensuse] Suse 10.3 install - oh dear (rant only)
    ... expectations" about the release? ... "The openSuSE 11.0 release will be the best openSuSE ... the first response above seems like someone is putting out the company line with political talking points like "all software has bugs" ... ... Why no response like, "All of the significant bugs Novell is aware of are fixed, and the RCs are running great on our test machines" "Your concern about 11.0 being a release with significant problems is way over blown Rankin." ...
    (SuSE)
  • Re: [opensuse] Suse 10.3 install - oh dear (rant only)
    ... remember Linux components come from a ... edge releases where there are expectations that the user community will ... find the many bugs that fall through the test harness net. ... So, if there is a bug in Kmail, should SuSE users castigate SuSE or ...
    (SuSE)
  • Re: [opensuse] Suse 10.3 install - oh dear (rant only)
    ... software is made by humans, it HAS bugs, and that is expected!!! ... expectations" about the release? ... "The openSuSE 11.0 release will be the best openSuSE ...
    (SuSE)
  • Re: 2.6.19 -mm merge plans
    ... I actually expected people to dislike arbitrary rules more than they do, but I've come to believe that people _like_ having rules that they have to obey, as long as it's not a big pain for them. ... So I think that a "odd release"/"even release" rule that clarifies what a certain mid-point in the release cycle actually _means_, even if it doesn't necessarily add anything else, might be a good thing. ... Then after people stop reporting show stoppers, change to rc numbers, where rc versions are actually candidates for release without known major bugs. ...
    (Linux-Kernel)
  • Re: Inheritance
    ... Go hooking to fix bugs in MS code? ... There's no site for reporting bugs in VS ... >> always be using the latest DDK. ... Maxim Shatskih, Windows DDK MVP ...
    (microsoft.public.development.device.drivers)