Hello. Are there lessons to be drawn from the problem discovered just after the recent release? Apart from pointing fingers, that is. :-}
I presume that people who voted for the release did as thorough a review as they could. And the problem is not primarily one of unit test coverage. Some use cases will always escape the scope of unit testing: It is not reasonable to extend the tests suite with all imaginable use cases. One thing that comes to mind would be to announce the release candidates on the "user" ML, gently requesting those users who intend to upgrade to test the JAR in as many of their applications as possible. ["Let them speak now or forever remain silent." ;-)] For backwards-compatible releases, that does not seem to be a huge burden on the people that use CM. What do you think? Regards, Gilles --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
