 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rune" <run### [at] mobilixnet dk> wrote in message
news:3bd88cfc@news.povray.org...
>
> > Would it be any help if I supplied an online perl-run db?
>
> > This wouldn't duplicate the beta-test ng - it would only
> > be for recording bugs that had been acknowledged in the
> > group...
>
> Well, I don't think that's what's needed. It won't be of any use if nobody
> maintains the list in the first place, as it only adds additional work to
> the maintaining job.
>
IMHO I don't think it would add additional work - rather the opposite.
a) it would serve as a common reference point for people to check against to see
if a bug they'd found had already been reported (this group's signal to noise
ratio can be a problem in that respect)
b) anyone could add to the db, but the understanding would be that they should
only do so after confirming with this group that they'd found a bug
c) like a) but for the bug-fixers to see which bugs were outstanding
Anyway, I'll go ahead and do it and then the pov-team can take a look and see if
it looks like a useful resource if no one has any objections? If it's no good,
the only time wasted is my own....
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: List of known bugs - any takers?
Date: 26 Oct 2001 06:33:45
Message: <3bd93c09@news.povray.org>
|
|
|
| |
| |
|
|
In article <3bd936bd$1@news.povray.org> , "Tom Melly" <tom### [at] tomandlucouk>
wrote:
> a) it would serve as a common reference point for people to check against to
> see if a bug they'd found had already been reported (this group's signal to
> noise ratio can be a problem in that respect)
>
> b) anyone could add to the db, but the understanding would be that they should
> only do so after confirming with this group that they'd found a bug
>
> c) like a) but for the bug-fixers to see which bugs were outstanding
>
> Anyway, I'll go ahead and do it and then the pov-team can take a look and see
> if it looks like a useful resource if no one has any objections? If it's no
> good, the only time wasted is my own....
This is just my own opinion, not speaking for the POV-Team:
The POV-Team already has a non-public* formal bug tracking system and is
aware of outstanding bugs once they find the way into our system (as our
time permits to enter that information there). I don't think anybody in the
team has the time to look at yet another tracking system and/or keep the
data consistent. A simple newsgroup message with a list is really
sufficient if it is up to date. If posted once a week every user should
really be able to read it before posting a bug report.
Thorsten
* If we would make it public we for sure would get lots of people
second-guessing why one or the other bug isn't fixed. Further, some bugs
are not related to POV-Ray directly but are internal issues that should be
changed sometime in the near or distant future...
____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde
Visit POV-Ray on the web: http://mac.povray.org
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3bd93c09@news.povray.org...
>
> This is just my own opinion, not speaking for the POV-Team:
>
> The POV-Team already has a non-public* formal bug tracking system and is
> aware of outstanding bugs once they find the way into our system (as our
> time permits to enter that information there). I don't think anybody in the
> team has the time to look at yet another tracking system and/or keep the
> data consistent. A simple newsgroup message with a list is really
> sufficient if it is up to date. If posted once a week every user should
> really be able to read it before posting a bug report.
>
Ahh! - I wrongly assumed that the posted bug list was the common reference for
the developers as well.
In that case, I withdraw my suggestion. Thanks for the info....
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Thorsten Froehlich who wrote:
>> Superellipsoid epsilon to big ?
>> http://news.povray.org/3b992a81@news.povray.org
>
>I cannot find anybody confirming this bug, maybe it got in this list by
>accident?
I can't find any previous confirmation, but a quick test shows that it
still does happen in 3.5b7 (Windows 98se. AMD K6-2 500. 128Mb.)
When the "radius" of the blob components is set very small, holes appear
in the blob surface.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
