[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 1.6.0 release update.

From: Neil Jerram
Subject: Re: 1.6.0 release update.
Date: 04 May 2001 23:27:06 +0100
User-agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7

>>>>> "thi" == thi  <address@hidden> writes:

    thi> well, i wouldn't want everything perfect (how boring!), but
    thi> at least we ought to strive for complete documentation.
    thi> spiffy new features plus poor documentation results in
    thi> backlash against the project, reducing slack.  this can be
    thi> avoided.

I'm all for striving, but I think it would be quite wrong to delay a
release until the documentation is `complete'.  We are as likely to
achieve perfect documentation as we are to achieve perfect code.

Also note that, the better the documentation gets, the more readers
are motivated to provide patches for small errors in it.  But readers
in general can't do that if the documentation hasn't been released!
So the overall process is accelerated by releasing the documentation
even when not yet complete, I think.

    thi> ok, i'll stop whining now and just request the doc task list
    thi> be posted or checked in so that i can see what i can do to
    thi> help in that area before It's Too Late... ;->

I'm afraid I'm not currently maintaining a doc task list.  Martin's
list is quite useful, but (as Martin also said) you can find things to
investigate simply by grepping for FIXME.  More generally, there is
still so much to do that tasks can be easily be identified just by
reading and reviewing the manual; with the current balance of finished
vs. not finished, I think that the burden of maintaining a complete to
do list would be more of a hindrance than a help.

On the other hand, I have a feeling that an `anti-todo' list might be
quite helpful (for both maintenance and readers); i.e. a list of the
parts of the manual that have been reviewed and are considered to be


reply via email to

[Prev in Thread] Current Thread [Next in Thread]