Development Checklist

[updated 12/12/2010 - suggestions are welcome]

1. Coding:
   • Core functionality (SQL, C, Python)
   • Use MADLIB_SCHEMA as the schema prefix.
   • Packaging and migrations (follow: PackMan notes)
2. Documentation (using Doxygen tags):
   • Write a user guide under under @namespace tag. See http://doc.madlibrary.org
   • Dev reference is (currently) just an unlimited version of the user doc. See http://devdoc.madlibrary.org
3. Unit tests:
   • Use PGXS regression tests
     • (Notes from PostgreSQL.org)
     • See example in the sketch method
4. Schedule code reviews (use Caleb, Gavin for now, unless you know someone else can help) using Crucible at http://codereview.madlibrary.org:
   • Initial code review on whole files.
   • Further code review on full files or specific commits.
5. Integration testing and QA:
   • Ask someone (you can also open a gitgub issue for tracking purposes)
   • We are currently looking for resources.