QA Manager for 3.6 Proposal

Candidate: Ian Walls

• Continue practice of minimum 1 signoff for patches from someone other than the author
• For larger devs and bug fixes, require a rigourous test plan
  • Tell the community how we can tell that your code actually works, and doesn't break other stuff.
• Push for more unit tests
• Push for a robust example DB to test against
  • This should be a full Koha database that can be loaded into MySQL and tested against.
  • Dates should be in relative SQL (CURDATE +/- days)
  • Lots of notes as to which patrons, items and holds are good for testing what kind of things
  • Addition of new data will be welcomed from any and all community members
• Regular reports to list and at IRC meetings of the statuses of devs that are 'in QA'

If possible, I'd also like to coordinate with area library schools, and get students to test parts of Koha for credit and experience. This is subject to many factors and thus cannot be promised, but it's an option I intend to explore.