I can't resist one more comment...
Delay the 1.2.1 FCS by two weeks and spend it documenting. And if you
happen to catch some bugs while you're documenting we'll all be MUCH
better off.
- John Wright
Starfire Research
Justin Couch wrote:
{snip}
> > to recommend to Sun the same thought that I feel - take a step back,
> > slow down, document and organize before proceeding with adding more
> > features. So I'll repeat my suggested priorities:
> > 1) Bug Fixes (reliable code)
> > 2) Documentation
> > 3) Performance tuning & new features (low priority)
>
> I agree. Documentation doesn't take long to do - 2 weeks most at max
> with people that understand the code. That is not going to hamper
> progress on new features. As soon as 1.2.1FCS is out, spend 2 weeks
> doing some documentation then hit 1.3/1.4.
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
