Frank,
You could work with Louis at Collabnet and setup a subcomponent for the Database Application. It would probably be a good idea to setup one for Accessing Data as well.
This way the CVS stays the same but you have a little more granularity in the issue process.
Frank Sch�nheit - Sun Microsystems, Inc. wrote:
Hi Peter,
Should there be a new component added to the issue tracker for the database?
Database access doesn't seem appropriate anymore and there are no subcomponents.
I suggest renaming "database access" to "Database" (there's in fact already an issue requesting this, though I didn't bother so far to find out what to do for this to happen :).
Introducing a new component has some ugly side effects, since a component is associated with a CVS repository (where our code then would not be located), default QA contacts for issues, and some more.
Ciao Frank
--
Scott Carr
OpenOffice.org
Documentation Co-Lead
http://documentation.openoffice.org
