 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'll bet that's what's really keeping POV 3.5 from coming out. Most bugs
must be sorted out by now.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Tony[B]" wrote:
> I'll bet that's what's really keeping POV 3.5 from coming out.
> Most bugs must be sorted out by now.
A year ago we also expected POV-Ray 3.5 to come out in a few months because
it'd already been so long. But it didn't. Who can say if most bugs are
sorted out by now or if it'll actually be another year before it is
released? ;)
Rune
--
3D images and anims, include files, tutorials and more:
Rune's World: http://rsj.mobilixnet.dk (updated June 26)
POV-Ray Users: http://rsj.mobilixnet.dk/povrayusers/
POV-Ray Webring: http://webring.povray.co.uk
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On Sat, 4 Aug 2001 15:48:28 -0500, Tony[B] wrote:
>I'll bet that's what's really keeping POV 3.5 from coming out. Most bugs
>must be sorted out by now.
Or waiting for the test renders to finish is the hardest part, all then
new features, in lots of different scenes, making sure they all work
together, seperately etc. Testing gets very boaring if you can't make
the program go wrong.
--
Cheers
Steve email mailto:ste### [at] zeropps uklinuxnet
%HAV-A-NICEDAY Error not enough coffee 0 pps.
web http://www.zeropps.uklinux.net/
or http://start.at/zero-pps
1:23am up 22 days, 3:25, 2 users, load average: 1.04, 1.01, 1.00
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> A year ago we also expected POV-Ray 3.5 to come out in a few months
because
> it'd already been so long. But it didn't. Who can say if most bugs are
> sorted out by now or if it'll actually be another year before it is
> released? ;)
I say release it sooner rather than later (beta worts and all) - cos you
know the pov community will just grab it and bug test it to the eyeballs for
you (some creative types may even code your fixes :)
--
Rick
Kitty5 WebDesign - http://Kitty5.com
Hi-Impact database driven web site design & e-commerce
TEL : +44 (01625) 266358 - FAX : +44 (01625) 611913 - ICQ : 15776037
POV-Ray News & Resources - http://Povray.co.uk
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rick [Kitty5] <ric### [at] kitty5com> wrote:
: I say release it sooner rather than later (beta worts and all)
I'd say better fix known bugs and shortcomings than release a buggy version.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> I'd say better fix known bugs and shortcomings than release a buggy
version.
but then it will never be released - you have to at some point come to the
decision that enough is enough and its time for a public beta - afterall
thats what beta is for....
--
Rick
Kitty5 WebDesign - http://Kitty5.com
Hi-Impact database driven web site design & e-commerce
TEL : +44 (01625) 266358 - FAX : +44 (01625) 611913 - ICQ : 15776037
POV-Ray News & Resources - http://Povray.co.uk
PGP Public Key
http://pgpkeys.mit.edu:11371/pks/lookup?op=get&search=0x231E1CEA
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Rick [Kitty5]" wrote:
>
> > I'd say better fix known bugs and shortcomings than release a buggy
> version.
>
> but then it will never be released - you have to at some point come to the
> decision that enough is enough and its time for a public beta - afterall
> thats what beta is for....
And this too will happen. At the moment things like final syntax
adjustments, big_bug_testing, example scene-file creation, and
documentation needs to be ironed out before the public beta testers
can get their hands on it. It sounds easy but it is not. This release
has a lot of new features, some of which are very complicated, and
will take longer to finish than say v3.1 did.
--
Ken Tyler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I guess it's better to wait. I've heard many don't use MegaPov because of bugs -
we wouldn't want the same for Pov 3.5 now would we?
- Nekar
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Rick [Kitty5] <ric### [at] kitty5com> wrote:
: but then it will never be released - you have to at some point come to the
: decision that enough is enough and its time for a public beta - afterall
: thats what beta is for....
I really don't understand this.
Firstly: There can only be a finite amount of bugs in a code. It can't take
an infinite time to fix them.
Secondly: What's the point in releasing a beta version with *KNOWN* bugs?
You say "that's what beta is for". No, it isn't. A beta release is to
discover unknown bugs, that is, bugs which testing did not find.
Releasing a beta with known bugs just causes tons of reports of those known
bugs. What's the point? "Thanks for your bug report, but we already knew
that". Kind of useless, isn't it?
(Don't bother answering with "but beta-testing can also discover unknown
bugs besides the known ones". Of course it can, but better get rid of the
known bugs first so that the developers can concentrate on the new ones which
come up with the beta testing.)
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> : but then it will never be released - you have to at some point come to the
> : decision that enough is enough and its time for a public beta - afterall
> : thats what beta is for....
>
> I really don't understand this.
>
> Firstly: There can only be a finite amount of bugs in a code. It can't take
> an infinite time to fix them.
I think that goes against the Law of Computing Entomology - 'There's
always one more bug'
;)
Bye for now,
Jamie.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
