[snip]
We should never have gotten into this situation, but I think the best
balance is:
1) do as much doc as is practically possible before the release
2) release as is to satisfy users demanding the fixes/features and to
reduce load on the users list (many faqs are addressed by things like a
javadoc and site release)
3) no more releases until the docs are in shape.
In principle I think that 3) should be enforced. Always. Releasing
components in an undocumented state means releasing them in an
unfinished state, which is shortsighted and irresponsible. It is unfair
towards users who don't regularly read the mailing list. 2) only gives
the impression that we are bending to those who do the loudest shouting.
I don't think it will reduce the load on the user list either, as most
users don't read javadocs. Those who demand fixes/features should use
snapshots, releases have to be complete.
As a crude, minimal compromise I could imagine putting a list of
undocumented features (or a documentation TODO) on the projects main
page. That would spare users some searching, avoid questions on the ml,
serve as a sort of contract for the release manager to fix these issues
before long, and finally, could incite some patches from people wanting
to contribute!
Just my opinion...
-Lukas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
