You're right, of course, as Thorsten was.

And though its perhaps to a certain degree my
fault, that "my" bug hasn't been looked at closer,
I would have thought that the community around here
would have helped as well. Thats what caused most
of my frustration, that dozens of people frequently
visit the beta-test groups, and comment, and do this
and that, but kept quiet while I was asking something
I find important, because it breaks an entire scene, not
only the object itself, or "some" shadows or whatever.
I'm not a natural bug-hunter, but from what
I've experienced in that group, some have the "knack"
to track the bug, even in larger scenes.

I just didn't get much help, thats what frustrated me,
not the POV-Team, which has a lot to do to not
only know the bug, but find the actual source in the
code and fix it - no easy task, I know from my own
programming experience.

Chris Cason wrote:

> As Thorsten pointed out, it is not possible to fix all bugs.
> We can't go on issuing betas forever. With a program as complex
> as POV-Ray, it is inevitable that there will always be some
> bugs. What our intention is, is to produce a release version
> that is stable, usable, and free of most (if not all) known
> -major- bugs. Minor bugs will be there, it's a fact of life.
>
> We within the team have been working on this release for more
> than two years and we feel that it's close to the point where
> we can release it to the public as non-beta software.
>
> And, as Thorsten also pointed out, once the source is released
> we expect that the user community will fix several of the bugs
> that we ourselves did not get the chance to do. It is quite
> likely that we will release bugfix versions of 3.5 fairly
> shortly after the initial release.
>
> -- Chris

--
Tim Nikias
Homepage: http://www.digitaltwilight.de/no_lights/index.html
Email: Tim### [at] gmxde

Post a reply to this message