Heikki Toivonen 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...
The alternative would be to log tasks in a proxy component and then
request the creation of a component because we have more than 10 items...
This seems artificial to me: if we are creating something new (e.g. the
dashboard), we shouldn't shy away of creating a component for it in
Bugzilla so that we can park tasks in there.
Cheers,
- Philippe
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
