On Wed, 12 Mar 2003 09:40, Nicola Ken Barozzi wrote:
Peter Donald wrote, On 11/03/2003 22.15: ...
...backward incompatible changes are all the rage in AValon these days. Supporting users is sooo yesterday.
It's not.
We will support users as much as we can. We've said it before, we say it again. Any incompatible change made was completely unintentional.
"saying" != "doing"
I hope you aren't implying that incompatibilities in this case are intentional?
What do you all think should be our unit test policy?
100% coverage and 100% passing for toolkits or as close to as possible. ie an example of good quality would be http://spice.sourceforge.net/configkit/clover/index.html
For integration components and containers we probably can't reasonably as stringent but should aim for high quality rather than this lets just change something and hope it compiles ... let alone works policy that is now in place.
Are you volunteering to help shore up our testcases?
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
