On Sat, 18 Feb 2006, Philippe Bossut wrote:
I would say that you should not create components until there are
actually bugs for that piece of code you are thinking about creating a
component for. And there should be several bugs (I'd say at least 10
bugs) and even then we should be reasonably sure that the piece of code
is not going away anytime soon.
I have to disagree here: we are trying to identify the new components we need
so that we can start logging tasks in Bugzilla. This happens before we have
code written for the component so, arguably, before we even have 1 bug...
Bugzilla != Taskzilla. The components should be organized in a way that makes
it easy for users to file bugs against existing code.
If we're really bent on using bugzilla for keeping track of development tasks
instead of just bugs how about creating a second bugzilla installation where
the components are designed for that purpose ?
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
