Fwd: REST APIs, and Tags

[Gervase Markham]

On 11/02/10 19:01, Frédéric Buclin wrote:
> IMO, an additional bug status doesn't fix anything. You move the problem
> from UNCO/NEW to NEW/READY.

Except that you can't file bugs as READY.

And there is a distinction between "yes, this is definitely a problem"
(-> NEW) and "this bug report is ready to be fixed" (-> READY).

> We don't *require* metadata, besides the component. You can ignore the
> OS/Platform fields if they are unimportant to you. Why again do you pay
> attention to them if they are meaningless for your team??

There is a cost to complexity which you pay even if you try and ignore
all the fields that you don't need.

What if, instead of having custom fields, we had hard-coded an
additional 3 of every custom field type into the default UI? When people
complained, we could have said: "why do you pay attention to them if you
aren't using them?"

>> plugins and tabs in Mozilla/Firefox. I need the ability to categorize
>> and organize bugs which are relevant to this effort.
> 
> Use the priority field. Use the target milestone field. Mark them as
> blocking some meta bug. And be sure they are in the correct component.
> What else cannot you do with that?

Because these fields can only reflect the view and the tracking of a
single person at once. (Well, perhaps multiple people can have meta bugs.)

Gerv
_______________________________________________
dev-apps-bugzilla mailing list
dev-apps-bugzilla at lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-apps-bugzilla