Re: Just random fixes with QC reports...

"Atle Smelvær" <atle@xxxxxxxxxxxxxx> wrote in
news:42988db7@xxxxxxxxxxxxxxxxxxxxxx:
>
> Ofcourse. Eliminating all bugs are impossible, and will always be. But
> we were talking about how long it takes to fix a easy reproduceable
> bugs. And it's nowhere near 100 hours... And I am also not saying that
> Borland should eliminate all bugs. Only those reported in QC before
> starting a new development cycle for the next major version. Because
> the list have been growing over the years, it may not be possible in
> one version. But if they do it right, it could be the situation after
> some releases.
>

Some years ago I worked for a company that produced a Fortran compiler.
They had a small team (2 people IIRC) whose sole job was to fix bugs. Each
month they fixed a small number of bugs, 5-10. Each month they would get
5-10 new bugs. Over a period of three years the number of outstanding bugs
did not decrease!

So, imagine that Borland experienced the same rate of productivity. How
many bugs are there outstanding, say 200? Assume that new bugs are
reported at the rate of 10/month. Then to eliminate all of the outstanding
bugs plus the newly reported bugs within 24 months would take approx 88 man
months, or 4 developers full time. That accounts for most of the existing
Delphi R&D team I think. And that doesn't even count in the QA testers.
So, would you be willing to have Borland completely stop all new
design/development on Delphi for the next 2 years in order to get all of
the outstanding bugs fixed?

Would Borland even be in business if they did that? Imagine what would
happen if Borland stopped delivering new functionality, stopped keeping up
with the changes in the market and the Windows operating system for 2 whole
years. Most of us would justifiably change to some other development
environment.



.

Relevant Pages

  • Re: Delphi QC Top Voted
    ... That priorization policy sounds logical for a developer who release a ... He could fix some now and the rest in a later SP. ... Borland released Delphi a year and a half ago, and no say that they will fix ... Take for example D7 IDE bugs. ...
    (borland.public.delphi.non-technical)
  • Re: Down to serious business -- possible fugitive from vb6
    ... to fix the bugs with the greatest ROI for the effort, ... Based on the past actions of Borland, many of whom are now with CodeGear, I don't believe that the correct decisions will necessarily be made. ... CG seems to be doing better, but there are still obvious examples in QC where 'bad bugs' still exist. ...
    (borland.public.delphi.non-technical)
  • Re: Just random fixes with QC reports...
    ... >> month they fixed a small number of bugs, ... imagine that Borland experienced the same rate of productivity. ... >> existing Delphi R&D team I think. ... >> get all of the outstanding bugs fixed? ...
    (borland.public.delphi.non-technical)
  • Re: Marcos latest Blog
    ... I know, they can't fix every bug, but the important ones, they need too. ... If I take the time to track down a big bug, Borland will actually fix it ... Just to give you an example, I have complained repeatedly about dbExpress drivers meta data bugs. ... Delphi would roll up their sleeves and fix the problems. ...
    (borland.public.delphi.non-technical)
  • Re: Defective Software
    ... Most software that I use on a regular basis has the bugs fixed that affect me. ... The ONLY exception is where the 'changeover' cost is too great -- for example, I once had a PCB layout program that had a large number of problems that weren't addressed. ... However, the 'changeover' cost from Windows is too high, and the changeover cost from Borland has been too high. ...
    (borland.public.delphi.non-technical)