Quality/QA-tools/OTS/DevelopmentGuidelines/Review

OTS Review Process

To get your contribution accepted please make sure the following points are fulfilled:

• Code must follow the coding standard: http://www.python.org/dev/peps/pep-0008/
• Code documented in epydoc format: http://epydoc.sourceforge.net/
• unit tests for all modified and new code: http://nedbatchelder.com/code/coverage/
• All old tests must pass

To speed up the review process please add the following information to your merge request or patch email:

• Description: A short description what the change does, how and why
• A link to the bug or feature in http://bugs.meego.com this contribution relates to
• Pylint output for the changed modules
• "epydoc --check" output for the changed modules. At least all public classes, modules, packages and methods/functions need to be documented.
• Unit test execution output (summary) for the changed modules
• Coverage report (summary) for the unit tests for changed modules