On Fri, 03 Sep 2004 11:01:58 -0400, Jim Charter <jrc### [at] msncom> wrote:
> > >I thought i provided some kind of bug report...
> > 
> > I would call it an 'impression' :-)
> > 
> > ABX
>
> Perhaps there could be a more public treatment on these groups of what 
> is correct bug reporting.

I think you are trying to think too seriously about sentence marked with a
smile. Hovewer if you really want to find an answer here I can say for myself
that it is not problem with "bug reporting" but "bug" definition. If the
binary delivered would create wrong output according to given script than this
is a bug. But if the output is correct but generated slowly than perhaps it is
slow io operations or poor compiler or not optimized algorithm but still
usable tool. I well understand it is not comfortable using such slow tool but
while I'm interested in listening any impressions from using MegaPOV, memory
leaks, broken pixels or security issues have highier priority in solving than
slow execution (thought we are still interested in such observations once we
release final MegaPOV 1.1 and will try to solve everything we are able to find
and fix). Sorry I can't define my understanding of "bug" any better due to
limited english. Perhaps I even use wrong word for expressing so I can only
sorry if I fail to meet your (seems native speaker) understanding :-(

Thanks for any feedback received from anyone during whole past beta existence.
Perhaps not everything was answered but all issues were at least investigated
and considered by the MegaPOV developers. I had a very limited free time in
past days but other MegaPOV fellows did a very good work on moving things
forward.

> I worked as a programmer, and in quality 
> assurance, for fifteen years

Welcome to the club. We are not young boys too ;-)

ABX

Post a reply to this message

ABX wrote:

> 
> I think you are trying to think too seriously about sentence marked with a
> smile. 

I took the smile as an invitation to discuss the problem further :)


Hovewer if you really want to find an answer here I can say for myself
> that it is not problem with "bug reporting" but "bug" definition. 

Okay, I see.  And in classic full project life cycle those definitions 
and their test beds would derive from the original user specifications, 
which obviously are not existent in this case.  Any system must 
prioritize for testing purposes. Is speed the emphasis? Usability? 
System integrity?  Or a reasonable balance?  Yes, now I understand the 
problem better.

If the
> binary delivered would create wrong output according to given script than this
> is a bug. But if the output is correct but generated slowly than perhaps it is
> slow io operations or poor compiler or not optimized algorithm but still
> usable tool. I well understand it is not comfortable using such slow tool but
> while I'm interested in listening any impressions from using MegaPOV, memory
> leaks, broken pixels or security issues have highier priority in solving than
> slow execution (thought we are still interested in such observations once we
> release final MegaPOV 1.1 and will try to solve everything we are able to find
> and fix). Sorry I can't define my understanding of "bug" any better due to
> limited english. Perhaps I even use wrong word for expressing so I can only
> sorry if I fail to meet your (seems native speaker) understanding :-(

I think in this case what was reported was the possibility that previous 
speed marks had been degraded in subsequent versions.  Without knowing 
that you consider this to be a reasonable compromise for other 
improvements, I can understand that someone might think they'd found 
something faulty.

> 
> Thanks for any feedback received from anyone during whole past beta existence.
> Perhaps not everything was answered but all issues were at least investigated
> and considered by the MegaPOV developers. I had a very limited free time in
> past days but other MegaPOV fellows did a very good work on moving things
> forward.
> 
> 
Well you would be welcome but I must concede that I don't report 
anything I come across because I don't relish having the "not a proper 
bug report" line thrown in my face.

Post a reply to this message