Mike Perham wrote:
-1 due to missing documentation.
John, I built the site but I don't see any documentation on the new
features and how to use them. Did I just miss something?
No, they weren't updated by those contributing patches. This mostly
occurred before we had our previous discussion about whether to accept
patches without docs.
Some sample
usecases would be helpful for people trying to understand when you use
one goal versus another. The "examples" link is an great example of
usecase documentation. Also the "Descriptor Format" link in the site
left menu gives me a 404.
You need to run modello:xdoc to get those. I thought it was wired in though.
I'm trying to think what the best option is here at the moment. I
certainly understand the need to catch up in the docs, but on the other
hand we have users begging for us to release features that are already
complete in SVN/patched in JIRA/etc. I have a queue of 14 plugins to
release here with all the bugs and patches cleared out.
I also know that several of us are away for two weeks due to JavaOne, so
when you factor in time to work on the docs, we're looking at 4-8
weeks to get all these plugins out.
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.
I also think that we need a better way to make the plugin docs
accessible. I'm concerned that an effort here right now is a bit wasted
as they are really hard to find.
What do others think?
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
