DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7442>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7442 Could the release guy please make sure that to include the actual release note for the release? Summary: Could the release guy please make sure that to include the actual release note for the release? Product: Tomcat 4 Version: 4.0.3 Final Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: Unknown AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] CC: [EMAIL PROTECTED] It is not the first time that I notice that the RELEASE-NOTES-4* files are out of date, wrong or misleading. For 4.0.3, it appears that RELEASE-NOTES-4.0.3.txt has been forgotten by someone. Also, may I suggest that the OLD release notes be merged into one file, for example OLD-RELEASE-NOTES.txt, and the CURRENT release notes, being in the release they *belong* to, be just named RELEASE-NOTES.txt. (Putting the version in the name obviously hasn't helped to keep it updated anyway, so why add have it there? And hving all those files just add clutter.) Also, renaming RELEASE-PLAN to PLANNED-RELEASES (OK, imagine .txt suffixes where applicable - I could do fine without, but I suppose it would bother Windoze users) would avoid some typing with tab-completion. I can understand documentation being out of order in development and beta releases, but in final versions please check the docs for at least trivial correctness. Either that, or leave docs out altogether. Good docs are slightly better than no docs, but bad docs are much worse than no docs. And false docs are just plain evil. -Lasse -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
