<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";
color:black;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=white lang=EN-US link=blue vlink=blue>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>What if a bug is pending something other
than a future release? What if the bug is pending another bug or if the
bug is pending customer feedback… Should that time count against
the engineer’s time to resolution? I agree that Target Milestone
will help. I agree that bugs that are postponed for another
target/milestone should be in a pending status. I’m adding
FUTURE_RELEASE to my pending reason list.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
color=black face="Times New Roman"><span style='font-size:12.0pt;color:windowtext'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 color=black face=Tahoma><span
style='font-size:10.0pt;font-family:Tahoma;color:windowtext;font-weight:bold'>From:</span></font></b><font
size=2 color=black face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma;
color:windowtext'> developers-owner@bugzilla.org
[mailto:developers-owner@bugzilla.org] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Lee Ivy<br>
<b><span style='font-weight:bold'>Sent:</span></b> Thursday, December 09, 2004 11:02
AM<br>
<b><span style='font-weight:bold'>To:</span></b> developers@bugzilla.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: Status: Resolved
Later</span></font><font color=black><span style='color:windowtext'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'>In my pre-Bugzilla days, we used the Target Milestone
approach and it worked well. A bug's Version showed what version the problem
was found in; if you didn't want to fix it right away you left it in the
Assigned state but set the Target Milestone for the future release where you
hoped (planned?) to fix it. The bug was still assigned to a developer, but it
was clear that bugs only needed to be fixed right away if their Target
Milestone matched the current release.<br>
<br>
I prefer this to Resolved/Remind -- as a QA guy, I think Resolved/Remind sounds
like a developer cop-out, "I am marking this resolved but I didn't
actually fix it, I just want to be reminded to fix it someday in the future --
trust me!". To me, moving a bug to Resolved implies a hand-off of
responsibility from development to QA, and that is not true for
Resolved/Remind.<br>
<br>
<i><span style='font-style:italic'>Lee Ivy<br>
QA Architect<br>
netZentry, Inc.<br>
<a href="mailto:lee@netzentry.com">lee@netzentry.com</a><br>
</span></i><br>
Stuart Donaldson wrote: <o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3 color=black
face="Times New Roman"><span style='font-size:12.0pt'>We wrestled with this,
and I am sure I saw somewhere the suggestion of using Target Milestones.
That is the strategy we have adopted. You can target this to any of the
builds on the current project, or target it to the next release, or set the
target to deferred which means some undetermined future release. <br>
<br>
I like the benefit of the required comments when using Resolve/Later, however
Later was not granular enough, and the paradigm seemed to fit the milestone
paradigm closer. <br>
<br>
<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
</body>
</html>