Contents 1 Release Checklist 1.1 1. Feature complete 1.2 2. Code review 1.3 3. Kwalitee 1.4 4. Documentation 1.5 5. Unit Tests 1.6 6. Component Tests 1.7 7. Demos 1.8 8. Installation 1.9 9. Stable system tests 1.10 10. Worker backward compatibility 1.11 11. Installation docs 2 Post Release 2.1 1. Update all the Wiki Pages 2.2 2.Epydoc

Release Checklist

1. Feature complete

Functionality of release fully documented and approved by Stakeholders OTS meets these requirements

2. Code review

• Code is readable and the intent clearly visible
• Bugs
• Check for presence of FIXMEs / TODOs / commented code and tests

3. Kwalitee

• epydoc
• pylint

4. Documentation

• Code is navigable with high level documentation
• Particular attention to public APIs
• Epydoc documentation compiled and published

5. Unit Tests

• All supported platforms
• All supported Python versions

1. coverage
2. unittests pass

6. Component Tests

• All supported platforms
• All supported Python versions

1. component tests pass

7. Demos

The demos included with the code work and are documented

8. Installation

• Documented
• Tested

9. Stable system tests

Full system tests have been running for a sustained period as part of a network with hardware

10. Worker backward compatibility

The Worker backward compatibility identified. Minimum Worker Version set in the Server.

11. Installation docs

Bring up to date

Post Release

1. Update all the Wiki Pages

• All links to code should be brought up-to-date

2.Epydoc

• Compile epydoc documentation and link from Wiki