Reviewing instructions
======================

Here are some steps that a reviewer should go through during a review:

- all public methods are documented (arguments, return value, exceptions)
  Important: check that @raises are present if a method is likely to throw an
             exception
  Important: add "MT safe." if the method can be called from multiple threads
             at the same time
- all public instance variables and class variables are documented
- Epydoc's generated documentation looks fine
- code style complies with the one explained in `coding style`_
- unit tests code coverage is reasonable (above 80% is a good indicator even
  though a manual checking of what is covered is important)
- FIXME should have been looked over; for big issues, tickets should be opened


When finished, check the maintainers listed are aware that they are
maintainers and put your name next in a maintainer variable: __maintainerX__

.. _coding style: /elisa/trac/wiki/CodingStyle
