| |||||||||||||
Bug systemsBug systemsPosted Aug 18, 2012 20:51 UTC (Sat) by epa (subscriber, #39769)In reply to: Bug systems by man_ls Parent article: Baron: The bug system I wish I had
On a big project like Mozilla with squillions of bugs, better metadata may help the bug ttacker scale better, even if it increases the constant factor of the amount of bookkeeping needed for one individual bug. I can well imagine that Mozilla developers will have a different viewpoint from those of us who've only worked on smaller projects.
(Log in to post comments)
Bug systems Posted Aug 18, 2012 21:06 UTC (Sat) by man_ls (subscriber, #15091) [Link] Truth be told, Baron specifies that the new sections should be optional always. So they would just increase the cognitive overload for bug reporters, but not necessarily the maintenance of bug records. There is some interesting speculation about keeping separate lists of permanent and transient comments. What I feel that the author needs is not more report fields, but some way to organize internal information. I think that the interface for the reporter and for the solver must be differentiated, and allow different things.There is also speculation about using boolean flags to keep state: instead of the myriad of combinations of status and resolution, keep separated flags for "confirmed", "solved", "verified", etc. In my experience, boolean flags win over status codes every time.
|
|||||||||||||