forked from madlib/archived_madlib
-
Notifications
You must be signed in to change notification settings - Fork 0
Development Checklist
jhellerstein edited this page Dec 21, 2010
·
7 revisions
[updated 12/12/2010 - suggestions are welcome]
- Coding:
- Core functionality (SQL, C, Python)
- Packaging and migrations (follow: PackMan notes)
- Documentation (using Doxygen tags):
- User guide (use @namespace tag >> see http://doc.madlibrary.org)
- Dev reference (http://devdoc.madlibrary.org)
- Write unit tests:
- Use PGXS regression tests
- (Notes from PostgreSQL.org)
- see example in the sketch method
- Use PGXS regression tests
- Schedule code reviews (use Caleb, Gavin for now, unless you know someone else can help):
- Initial code review on whole files.
- Further code review on full files or specific commits.
- Integration testing and QA:
- Ask someone (you can open a gitgub issue for tracking purposes)
- We are looking for resources.