Home
The Toolkit for Online Communities
17508 Community Members, 1 member online, 2326 visitors today
Log In Register
OpenACS Home : Forums : OpenACS Development : Software Development (Bugs, QA, etc) and OACS : One Message

Forum OpenACS Development: Response to Software Development (Bugs, QA, etc) and OACS

Collapse
Posted by Lars Pind on
I have some data model sketches at http://pinds.com/tmp/bug-tracker-outline.sql, but otherwise it's still mostly in my head.

Any experts in acs-relationships and all that crud out there who can help me with some of the details on that? It would seem to me that that would be the right way to model relationship between bugs (duplicate, depends on/blocks, just related, ...), user interest/"notify me", mapping tickets with patches, assignments, maybe even mapping bt_code_values to bt_tickets.

Any comments on that assumption? Is that the right way? Will it perform? Will it be more trouble than it's worth? Any implementation hints?