Thomas de Groot <tho### [at] degrootorg> wrote:
> On 10-11-2013 14:31, clipka wrote:
> > Reports of the +C bug appeared only a short time ago, while we had
> > already begun the last preparations for the actual release (which had
> > virtually nothing to do with changes to the code; stuff like making the
> > switch to the new license, setting up the Git repository, and other such
> > stuff).
> >
> > It seems that in this last phase, povray.beta-test hasn't been read by
> > any of the developers on a regular basis, so we weren't even aware of
> > these +C artifacts and their severity; from what I see now they would
> > indeed have warranted halting the release process.
> >
> > It should be mentioned that while povray.beta-test is a good place to
> > discuss /suspected/ issues, the most reliable way of communicating
> > /identified/ issues is via http://bugs.povray.org. New entries there
> > trigger an email to the members of the dev team.
> >
>
> Yes, I forgot to file a bug report indeed, so I take the blunt impact of
> the responsibility :-)
>
> I shall try to reproduce the problem. However, I have not noticed it in
> any of my later renders, since my mention of it. So, it may be fairly
> difficult to do, especially to make it reproducible. :-(
>
> Thomas

Sometimes I'm a bit fast with nitpicking I fear. But in the first discussion
about this problem Chris Cason himself stated that this issue would be a main
obstacle to release 3.7 finally. I could have filed a bug report too, so Thomas
is not the only one to be blamed. On the other side, playing more and more with
the new additions to the Windows editor, e.g. having a texture menu with
pictures and so on (may be I have not noticed that earlier, but I think this is
new) and all the other additions from 3.6 to 3.7 (sslt e.g.) I now think, that a
final release is suited. I don't apologize for my first opinion - since one
cannot apologize for an opinion - but I changed my opinion now, playing around
with this wonderful version.

Best regards,
Michael

Post a reply to this message