API docs updated nightly

[Ethan Blanton]

Luke Schierer spake unto us the following wisdom:
> > Should the online API docs be built nightly at all?  I'm of the
> > opinion that they should probably be for the most recent released
> > version, myself.
> 
> Released based API docs are best for plugin authors.  MTN based API docs
> are best for Summer of Code students, and those developers looking at
> bugs in areas of the code they have not worked with in a while.

My opinion is that anyone working on the codebase itself obviously has
the source, and the documentation is in said source.  There is no
reason that a plugin author need have the source, however, which is
why I believe the online documentation should reflect released
versions.

I personally find the header files and tags more useful than the
doxygen output, myself, which is another reason I feel that
up-to-the-minute web documentation is not as useful as release
documentation.

However, Daniel says we can have both -- which seems like the
appropriate solution, to me.

Ethan

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://pidgin.im/pipermail/devel/attachments/20070924/2d696a41/attachment.sig>