Re: TeamB, bugs and waste of time...

From: Alessandro Federici (alef_at_remobjects[remove-this)
Date: 01/07/04 

Date: Wed, 7 Jan 2004 16:57:34 -0600

"Wayne Niddery [TeamB]" <wniddery@chaffaci.on.ca> wrote in message
news:3ffc85a2@newsgroups.borland.com...
[..]
> There is nothing wrong with this idea - of course bugs can be discussed
> here. But these newsgroups are not just for reporting bugs, they are for
> getting help in using the products. The ratio of bug reports vs everything
> else is low, the *completeness and quality* of the information posted here
> as a "bug report" is typically low and would require at least some and
> sometimes a lot of follow up before a worthwhile entry can be made.

Wayne, this will be my last post on the matter but I will try to explain at
my best, again, what I meant initially.

As you correctly said (and I pointed out before) the amount of bugs reported
in this newsgroups are minimal so let's not exxagerate talking about family
time and stuff like that.

**Sometimes** it happens that a bug is instead very well reported (along
with a test case) like it recently happened with the D8/C#B streaming issue
OR that it gets reported so many times that is easy to understand there's an
issue. So, when we have situations like that I would think it's much simpler
and surely takes less time for TeamB (a TeamQC would be nice to create! <G>)
to just enter the damn thing in QC rather than keep asying "did you enter
it? If you didn't you cannot expect Borland to know they have bugs/you bad
boy" or the many nonseses that have been written/responded to in that
thread.
Those surely took much more time away from families or work than just saying
"We logged it. Thanks for the report. Next time make sure to enter it in
QC". There are tens and tens of TeamB posts in that creepy thread. Almost as
many as those generated by Captain Joke's newsgroup reader! I cannot believe
that entering a bug in QC **as a courtesy once or twice a month** can be the
big deal you guys make it appear and yes, I have worked as beta tester for
over a year so I know *very well* how that stuff is done and works.

Gone,
  Alessandro

Relevant Pages

  • 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)
  • Re: First day with production development on D2005
    ... >> involved in reporting them vs. the benefit of reporting them. ... > The cost is taking some time to write the report. ... bugs are unlikely to get fixed and that show-stopper, ... not bother reporting bugs and if the development environment has too many ...
    (borland.public.delphi.non-technical)
  • Re: Wolfram Alpha claims to be a primary source.
    ... D> But your manner of reporting bugs, ... D> newsgroups in a dramatic way is not the best approach. ... It's probably not an unreasonable assumption that had Vladimir been professional about the way he reported bugs, he may well have been considered for employment by Maplesoft, Wolfram Research, perhaps Mathworks too. ...
    (sci.math.symbolic)
  • Re: Delphi 2007 more Flakey than 2006?
    ... I don't know how difficult this would be - as my bugs are all my own ... Windows has such a reporting system on board - called WER (Windows ... which attaches the stack trace similar to what Windows error ...
    (borland.public.delphi.non-technical)
Loading