My next assualt on the todo's will be related to this.
WILL
----- Original Message ----- From: "Nathan Bubna" <[EMAIL PROTECTED]>
1. published javadoc and user's guide type stuff should match latest released version (including betas and release candidates to encourage early adoption).
+1
2. published change log or other "news" type pages should be regularly updated to show changes since last release (also to encourage early adoption)
+1. I did this recently (updated change log). I'd like to reformat this, tie it closer to the issues list
3. typos in published javadoc or user's guide should be fixed to match latest release's actual functioning, even if that puts them at odds with the docs bundled along with that release.
+1 on concept, but not sure how we'd manage this. Does this mean we need to keep the branches up to date? Could get confusing.
4. any docs that do not reflect the latest release--whether because they are obsolete or cutting edge--should not be placed or left up on the project web site
+1. Great idea. We've already talked about getting rid of the specifications docs.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
