Monthly Build Goals: Difference between revisions
From ParaQ Wiki
Jump to navigationJump to search
Line 10: | Line 10: | ||
|- | |- | ||
! 001 | ! 001 | ||
! | ! BG | ||
| | | | ||
| Reformat repository | | Reformat repository | ||
Line 16: | Line 16: | ||
|- | |- | ||
! 002 | ! 002 | ||
! | ! BG | ||
| | | | ||
| Doxygen operates on entire repository | | Doxygen operates on entire repository | ||
Line 22: | Line 22: | ||
|- | |- | ||
! 003 | ! 003 | ||
! | ! BG | ||
| | | | ||
| Code properly commented (so Doxgen works on the entire repository | | Code properly commented (so Doxgen works on the entire repository | ||
Line 28: | Line 28: | ||
|- | |- | ||
! 004 | ! 004 | ||
! | ! BG | ||
| | | | ||
| Dashboard is green. BG will pursue miscreants and ne'er-do-wells | | Dashboard is green. BG will pursue miscreants and ne'er-do-wells | ||
Line 34: | Line 34: | ||
|- | |- | ||
! 005 | ! 005 | ||
! | ! BG | ||
| | | | ||
| Adequate code coverage | | Adequate code coverage | ||
Line 49: | Line 49: | ||
| | | | ||
| Demo-specific code removed | | Demo-specific code removed | ||
|- | |||
|- | |||
! 008 | |||
! DR | |||
| | |||
| Action Items should be put into bug tracker | |||
|- | |- | ||
|} | |} |
Revision as of 13:47, 15 March 2006
March (release date Friday, March 31)
Initial executable release, not intended to be released to users. This is a chance for us to get our repository ready for full-on development, and get Testing, Coverage, and Testplans in place.
Action Items
Item | Who | Status | Desc. |
---|---|---|---|
001 | BG | Reformat repository | |
002 | BG | Doxygen operates on entire repository | |
003 | BG | Code properly commented (so Doxgen works on the entire repository | |
004 | BG | Dashboard is green. BG will pursue miscreants and ne'er-do-wells | |
005 | BG | Adequate code coverage | |
006 | ETI | Auto-generated object inspectors should be improved. In particular, useful widgets when possible, and the most eye-pleasing design possible. A general goal is that the automatically-generated object inspectors should be as well-designed, useful, and pleasing to the eye as possible. | |
007 | ETI/TS | Demo-specific code removed | |
008 | DR | Action Items should be put into bug tracker |
April (release date Friday, April 28th)
- Full support for building pipelines, including:
- 3D widgets
- Pipeline editor with fan-out support (user can easily understand connections, types of objects, state of those objects)
- Undo/Redo on all operations
- File->Open, File->Save, File-Save As, File->New all need to work.
- Initial Release Test Plan, captured in a recorded test.