Daniel John Debrunner wrote:
>Not sure how we can get people to scratch the code coverage itch. It
>seems we can't get a lot of folks interested in fixing the 150+ bugs out
>there, never mind writing more tests that might uncover more bugs. I
>would love it if we could find a way.
>
>Bottom line is that if people don't care about code coverage they are
>not going to work on improving it.
>
>
Well, there is scratch your own itch and then there is the "Apache Way".
>From http://www.apache.org/foundation/how-it-works.html
<quote>
*Philosophy*
While there is not an official list, these six principles have been
cited as the core beliefs of philosophy behind the foundation, which is
normally referred to as "The Apache Way":
- collaborative software development
- commercial-friendly standard license
- consistently high quality software
- respectful, honest, technical-based interaction
- faithful implementation of standards
- security as a mandatory feature
All of the ASF projects share these principles.
</quote>
Code coverage, reducing bug backlog and addressing functional testing
and security issues are part of our responsibility as an ASF
project. Where do we rate for each of the six principles on a scale
of 1-10 for embedded and client? Where should we be? How do we get there?
Kathey
