> > > > Or do we don't bother adding this information at all and revisit at a > later date? Anyone have a strong view on this? > > Thanks, > Justin > > I do think we should figure out what the proper values are to reduce the amount of work we have to do when its time to package a release by not having to go through the entire SDK to make sure all the documentation is ready.
Maybe this becomes part of patch acceptance? Perhaps as part of accepting a patch we require that the code has the required documentation and automated tests to verify and we provide guidelines for authoring them? I'm going to try to dig through some other Apache projects and see if they define this somehow on their project sites, or perhaps a mentor can provide some guidance here? -omar
