: distribution, we should start documenting their changes. I suggest that we : add a file contrib/CHANGES.txt. This way we don't pollute the top-level : changes file. Having one changes file per contrib project on the other : hand makes it more difficult to get an overview, so one in contrib seems : like a good compromise. Objections?
I think it would be a great idea if every contrib module had a CHANGES.txt (and while we're at it: a README.txt) which was copied into the releases (side by side with the respective jars) Having a single contrib/CHANGES.txt is also a good idea ... but perhaps that could be generated at build time from the individual contrib/*/CHANGES.txt using the ant <concat> task? That way you get the best of both worlds: individual CHANGES.txt files for the specific modules, and a general CHANGES.txt for the contrib directory as a whole. -Hoss --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
