Vincent Keunen wrote:
> > First, I must say that I agree with 2 comments from Noel:
> > > Internal Documentation
> > > Absolutely necessary. But NOT to hold up the 2.1 release. We can
continue
> > > to upgrade the web site with new documentation, and any serious
developer
> > > should be working from the CVS
> You wouldn't release Documentation with no code would you?
> Why would you release code with no documentation?  If documentation
> isn't a condition for release, you'll never do it.

Everyone is agreeing that the documentation is necessary.  But javadocs for
developers is not a reason to hold end users hostage.  The psychology is
backwards.  The documentation is getting done, but telling developers who
can get the current code from the CVS that there won't be a user release
until there is developer documentation is not going to incent them to do
javadocs.  If they don't care, they don't care, and they aren't the ones
being held hostage by this false incentive.  Fortunately, Peter has both
time and interest, and he is doing a great job of updating the internal
documentation.

>> javadocs are for developers. I view 2.1 as a RELEASE build for users.
>> Yes, we need to work on the javadocs, but I would not wait for them
>> before putting out a stable release build if we can do so.

> retranslate:  "Code quality is not important"

Overly simplistic software cliche.  2.1 is superior in all ways to 2.0a3,
including javadocs (albiet incomplete).

Ironically, I just answered a question from someone who downloaded 2.0a3
over a week ago, and ran into the erroneous end user documentation.
Releasing 2.1, which has CORRECT documentation would have saved that person
10 days of grief.  Sure, it would have saved me the 30 seconds it took to
reply, but it would have saved him 10 days.

At the least, I do not see any reason not to replace 2.1a1 with a 2.1a2
Milestone Build based upon what we have now, and invite end users to help
out with the user documentation.  The CVS HEAD currently fills all the
criteria necessary for a Milestone Build.

        --- Noel


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to