<html 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)">
<style>
<!--
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.Author, li.Author, div.Author
{margin:0in;
margin-bottom:.0001pt;
text-align:center;
font-size:12.0pt;
font-family:"Times New Roman";
font-style:italic;}
span.EmailStyle18
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:8.5in 11.0in;
margin:.5in .5in .5in .5in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>So everyone knows, I considered re-opening 141175, but
elected to have an open discussion about this here first.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>A decision was made to make bug 141175 a dupe of bug 81642
some time ago. Bug 141175 asks for a “sub-bug” feature, and
bug 81642 is resolved as fixed having created the bug cloning feature.
That’s no problem as it helps move us toward the goal, but what I’m
seeing is a real need for “sub-issue” identification. I am
aware of meta bugs as a method dealing with sub-issues, however, it doesn’t
really address the problem we’re having.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Say, we find that one issue exists across ten different
languages, but each of those needs to be addressed separately. At this
point, there really isn’t an easy way to let users specify that updates
to a dependent bug are also made in the parent. This is important because
we’re looking for a way to create a tracking bug giving us the ability to
see what’s happening with all the dependencies, but at the same time,
find a way that will make it possible to enter an update that goes either at
the “overall” scope or at the “individual issue” scope
and be distributed properly. <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Here’s what I see right now on the way of possible
interactions:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>The parent bug needs to be updated when an update needs to
go to everyone. The problem is, that doesn’t update any
descriptions of any children.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>An update goes into a child bug appropriately, but none of
the other children need to be updated. Still, the parent does need to be
updated.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>One potential solution I see for solving this is to have a
new field that may be set when a bug is a parent of other bugs modifying the
way the bugs are updated so children are seen as “sub-bugs.”
Normal updates happen no matter what the field’s value is, but if the
field is set properly, updates in longdescs are propagated according to
additional rules (like above). Either that or something similar could be
done with the dependencies table, creating a new sub_bug flag denoting whether
or not a bug was a std. dependency or a “sub-bug” issue.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I’m just “free-thinking” about this at the
moment and would like any feedback you may want to offer.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=blue face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:blue'>---<br>
Kevin Benton<br>
Perl/Bugzilla Developer/Administrator, Perforce SCM Administrator<br>
Personal Computing Systems Group<br>
Advanced Micro Devices</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'> <o:p></o:p></span></font></p>
<p class=MsoNormal><font size=1 color=blue face=Arial><span style='font-size:
7.5pt;font-family:Arial;color:blue'>The opinions stated in this communication
do not necessarily reflect the view of Advanced Micro Devices and have not been
reviewed by management. This communication may contain sensitive and/or
confidential and/or proprietary information. Distribution of such
information is strictly prohibited without prior consent of Advanced Micro
Devices. This communication is for the intended recipient(s) only.
If you have received this communication in error, please notify the sender,
then destroy any remaining copies of this communication.</span></font><o:p></o:p></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</body>
</html>