Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] STP Committer/Developer commit process page

Great draft! A couple of comments below:

Becoming a committer
Every developer's contribution is welcomed. And by the time, developers can become committers.
Replace 'by the time' with 'in time'.
Automated tests: all code should come with automated tests, which should run as part of the overall test cycle. The build-system provides a test coverage measurement tool. Test coverage should be as high as possible, but certainly not below 70%.
I strongly agree with this test-gated approach, or +1 as they say these
days. One such tool that we may use is Cobertura (http:// cobertura.sourceforge.net/)
which is a jcoverage fork, provided that license compatibility can
be established appropriately - the Corbertura ant tasks are Apache,
the code itself is GPL. Once we do not include instrumented class
files in the dist, we are ok I think, even though IANAL.

 rgds
  --oh


Back to the top