We should remember, though, to add a comment saying which ticket this
is a duplicate of. If this is genuinely a new bug then we need to establish whether
the ticket contains enough information to proceed or not. If not then we may need
to enter into a dialog with the reporter to obtain more information. Determining
whether a bug is reproducible also saves us time??”if the bug only manifests itself
for the reporter then our developer will have a harder time trying to fix it. Lastly
deciding how severe the bug is lets us prioritize our bugs, and again Trac provides a
mechanism for this through the severity field within tickets.
??? ??? ??? ???
Chapter 7
[ 79 ]
Once we have a triaged bug then we need to ask the same if, when, and who
questions as we did for a feature. Although we like to fix every single bug, the simple
reality is that we cannot. First we need to decide if we are going to fix it, a decision
most likely based on how severe it is and whether we can reproduce it. Trac provides
us with the wontfix resolution for tickets that we are never going to address. For
the bugs we are going to address, we should now target them to milestones just as
we did for features. Here the secret is to be realistic about the bugs we are going
to address in each milestone??”if we assign all to the next milestone we will never
reach it.
Pages:
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110