----- Original Message -----
From: "Nick Coghlan" <ncoghlan(a)redhat.com>
To: "beaker-devel" <beaker-devel(a)lists.fedorahosted.org>
Sent: Monday, May 13, 2013 1:44:24 PM
Subject: [Beaker-devel] Defining a more useful component list in Bugzilla
The current component list in Bugzilla has a few limitations, with some
bugs being thrown at a component more or less at random, since they
don't fit any of the existing components. In other cases, the component
is too broad, failing to make appropriate distinctions in the assignments.
Here's the current component list:
command line
Doc
inventory
qpid
lab controller
scheduler
reports
tests
test harness
web UI
Those actually aren't *that* bad, there are just some missing ones and a
couple could do with a name change.
Suggested name/scope changes:
qpid -> notifications (covering both AMQP sending and receiving and
email sending)
tests -> test suite
inventory -> inventory task
test harness -> beah test harness
command line -> bkr CLI
Suggested new components:
beaker-wizard CLI
other tasks (covers all standard tasks other than the inventory task)
harness API (for the new stable harness API)
server XML-RPC (for central issues that aren't related to the web
UI or scheduler)
multiple (problem/feature that spans multiple components)
unknown (for bugs that haven't been triaged yet)
Fedora compatibility
I'm *not* sure those proposals actually make sense, but I wanted to
provide a starting point for discussion.
+1
Cheers,
Nick.
--
Nick Coghlan
Red Hat Infrastructure Engineering & Development, Brisbane
Test Automation Team Lead
Beaker Development Lead (
http://beaker-project.org/)
PulpDist Development Lead (
http://pulpdist.readthedocs.org)
_______________________________________________
Beaker-devel mailing list
Beaker-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/beaker-devel