[Dev] Last call: bugzilla components proposal
Katie Capps Parlante
capps at osafoundation.org
Tue Feb 21 15:55:47 PST 2006
The current decision is to use bugzilla to track tasks as well as bugs.
The app team has been using bugzilla this way for nearly a year
most of the platform team has agreed to try using bugzilla this way for
0.7. Tracking bugs and tasks in one instance of bugzilla allows us to
track the work in one place, one of the reasons we chose to do this even
though bugzilla has some flaws as a task tracker.
Given that decision, we need the components to support our work. I'm
confident that we can come up with a reasonable set of components that
support both tasks and bugs. I understand that you respectfully disagree
with using bugzilla for task tracking, but as it is working reasonably
well for the apps team, we're going to go with the group decision.
Andi Vajda wrote:
> 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 ?
> _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
> Open Source Applications Foundation "Dev" mailing list
More information about the Dev