On Tue, Jul 21, 2009 at 7:45 PM, Chris Hostetter<[email protected]> wrote:
> To me, the key is to make sure all functionality is documented *somewhere* > before it gets committed. if it makes sense in javadocs great, if it's > too widespread to fit neatly into the javadoc method/class/package > structure, a wiki ting everything together is handy. +1 I think for many of Lucene's features, good javadocs is what we need... and then for big features, good javadocs plus a wiki page makes sense. Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
