Calendar Talk:Bugzilla Components: Difference between revisions

Jump to navigation Jump to search
separate issues by proposal
m (link to establish component names)
(separate issues by proposal)
Line 1: Line 1:
===Process issues===
==Process issues==


Q. What happens to bugs in deleted categories?
Q. What happens to bugs in deleted categories?
Line 10: Line 10:




===Goal Issues===
==Goal Issues==


Q. What are reasons for making change now?
Q. What are reasons for making change now?
Line 21: Line 21:
* A set of proposed eventual categories to meet these goals: [[Calendar:Bugzilla_Components:Proposal_By_Function]]
* A set of proposed eventual categories to meet these goals: [[Calendar:Bugzilla_Components:Proposal_By_Function]]


=== Comments from mvl ===
My comments: The less components, the better. More components will only create confusion, bugs moved between components, bugspam, useless comments etc.
I will see all bugs anyway. We don't have tons of very specialized developers, the devs we have will have to look at everything anyway.
<blockquote><em>(This points out categories are not just for separation, but also for gathering bugs that might otherwise be filed under different terms.  Added goal [http://wiki.mozilla.org/Calendar:Bugzilla_Components:Goals#establish-component-names establish component names]. [[User:Gekacheka|Gekacheka]] 20:59, 6 Oct 2005 (PDT))</em></blockquote>


===Particular component issues===
<blockquote><em>(MVL's comment seems to argue for just one component, 'General'.  I think we should try to make the calendar bugzilla database more accessible to potential reporters, triagers, and patch contributors who don't see every bug, and therefore can use some help providing the right names when searching for duplicates, or relating the bug database to a component-name based roadmap such as [[http://wiki.mozilla.org/Calendar_Talk:Roadmap#Sunbird_0.3a2_goals.2Ftasklist]].  Changes in component will likely be in conjunction with confirming the bug or changing the summary, so it probably won't add significantly to the bugzilla mail.  When reporters choose from a list of component names, they may be less likely to use a synonym, so the component name won't need to be added to the summary as often.  [[User:Gekacheka|Gekacheka]] 06:53, 12 Nov 2005 (PST))</em></blockquote>
 
 
==Proposal 1 issues==


Q. It's not clear what goes in 'base'?  Should all UI be removed from it?
Q. It's not clear what goes in 'base'?  Should all UI be removed from it?
Line 29: Line 37:
* current proposal has separate category for preferences, and for day/week/multiweek/month view,  
* current proposal has separate category for preferences, and for day/week/multiweek/month view,  
* but not say for list/search/filter views, date pickers, event/task dialog, nor for import/export, alarms, printing, ...
* but not say for list/search/filter views, date pickers, event/task dialog, nor for import/export, alarms, printing, ...
* at what time would it be appropriate to eventually add these categories?
* under what condition would it be appropriate to eventually add these categories?
 
 
==Proposal 2 issues==


Q. Is it ok to rename "Help Documentation" to "Web pages/documentation"?
Q. Is it ok to rename "Help Documentation" to "Web pages/documentation"?
* The category holds bugs about the web site, not the calendar online help, which is managed separately at the [http://calendarhelp.mozdev.org/bugs.html calendarhelp] project.
* The category holds bugs about the web site, not the calendar online help, which is managed separately at the [http://calendarhelp.mozdev.org/bugs.html calendarhelp] project.


==Proposal 3 issues==
Q. why do 3 of the providers get their own bugzilla component?  What about bugs in the remaining providers? 
* Should all 5 providers get their own bugzilla component? 
* Should all 5 providers be one bugzilla component?  ([[User:Gekacheka|Gekacheka]] 06:53, 12 Nov 2005 (PST))
==Proposal 4 issues==


== Comments from mvl ==
Q. May be difficult for reporters to tell whether a bug is, say, sunbird-only or general, so triage may still have to recategorize some bugs.  
My comments: The less components, the better. More components will only create confusion, bugs moved between components, bugspam, useless comments etc.
I will see all bugs anyway. We don't have tons of very specialized developers, the devs we have will have to look at everything anyway.


<blockquote><em>(This points out categories are not just for separation, but also for gathering bugs that might otherwise be filed under different terms.  Added goal [http://wiki.mozilla.org/Calendar:Bugzilla_Components:Goals#establish-component-names establish component names]. [[User:Gekacheka|Gekacheka]] 20:59, 6 Oct 2005 (PDT))</em></blockquote>
Q. Relies on keyword search to find bugs for each component, so triagers will need to make sure summary has correct keyword (no menu of choices).  ([[User:Gekacheka|Gekacheka]] 06:53, 12 Nov 2005 (PST))
101

edits

Navigation menu