X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88AFB.7B6B3DB8@onstor-exch02.onstor.net>; Thu, 20 Mar 2008 19:30:09 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88AFB.7B6B3DB8"
Content-class: urn:content-classes:message
Subject: RE: updating defects
Date: Thu, 20 Mar 2008 19:30:08 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08FC3327@onstor-exch02.onstor.net>
In-Reply-To: <6CF28FDE-9912-4738-948E-8DD8541C1E05@onstor.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: updating defects
Thread-Index: AciK+rGtaQIlFTrjRdyWM09f3izsxAAAJonw
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "Ian Brown" <ian.brown@onstor.com>
Cc: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>,
	"Larry Scheer" <larry.scheer@onstor.com>,
	"Jobi Ariyamannil" <jobi.ariyamannil@onstor.com>,
	"dl-Cougar" <dl-Cougar@onstor.com>,
	"dl-Software" <dl-software@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C88AFB.7B6B3DB8
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Because one again some people don't update the p4 number field. They
just put a . or space in the field.
Other than this, it may work if we filter the changes that were made to
the dev branch.


________________________________

	From: Ian Brown=20
	Sent: Thursday, March 20, 2008 6:25 PM
	To: Tim Gardner
	Cc: Maxim Kozlovsky; Larry Scheer; Jobi Ariyamannil; dl-Cougar;
dl-Software
	Subject: Re: updating defects
=09
=09
	Why don't we do this automatically, put your p4 check in number
into the bug -- which we do, then just search for every bug with a p4
checkin number between the two submittal p4 numbers -- doesn't that
solve the problem?=20


	On Mar 20, 2008, at 7:17 PM, Tim Gardner wrote:


	Max,=20

	Please don't do this. Larry has enough on his plate with his
cougar tasks and taking over for Ken.=20
	He is also responsible for writing the submittal notes. To do
this he relies on the info in clearquest being correct.=20
	Putting incorrect info in the defect makes his work harder or
causes the submittal notes to be incorrect.=20
	If you don't want to take the time to put the correct info in
each defect you fix then perhaps you would like to be=20
	responsible for writing the submittal notes. Let me know. I'm
sure Larry would glady have you take over this task.=20
	I'm sure there is a better way to do this. We are open to
suggestions. But at the same time we have very limited=20
	resources for this kind of work at the moment.=20

	Tim=20


		_____________________________________________=20
		From:   Maxim Kozlovsky =20
		Sent:   Thursday, March 20, 2008 4:02 PM=20
		To:     Larry Scheer; Jobi Ariyamannil; Tim Gardner;
dl-Cougar; dl-Software=20
		Subject:        RE: updating defects=20

		Is it a big deal if the build in is off by three? Or by
4? When does the big deal start exactly? Instead of tolerating putting
incorrect information in the defect it would be much better for
everybody if this information would be updated when the submittal is
actually produced. You know the changes you have selected for the
submittal. You can find all the defects that have state fixed with the
change numbers from this submittal. This produces the list of the
defects that have been fixed in the submittal without any guess work and
without any possibility of producing incorrect information.=20

		I am just going to continue putting incorrect
information there as a reminder for you that you have to fix the
process.=20

		_____________________________________________
		From: Larry Scheer
		Sent: Thursday, March 20, 2008 3:58 PM
		To: Jobi Ariyamannil; Tim Gardner; dl-Cougar;
dl-Software
		Subject: RE: updating defects=20

		Yes, this is an issue. Before I started doing the
submittals I didn't know what to put at times for the build so I usually
just put what I thought was the next build. As long as it is close and
as meaningful, by this I mean not random and at least the "for project
field" matches the project that you are working on.

		My request is for an honest attempt/guess to get it
"right."  It is no big deal if it the "build in" is off by one or two.
Tim asked for diligence, I asked for a bit more kindness and awareness
when entering the data. We all know were the weak spots and irritations
are. We know that it will accept random garbage in many of the fields.
I'm just saying, asking, that people don't defeat the intention of the
tool just because they can, or feeling grumpy. I imagine it is going to
be a while before anyone gets around to fixing the defects in the defect
tracking tool.

		_____________________________________________
		From: Jobi Ariyamannil
		Sent: Thursday, March 20, 2008 2:46 PM
		To: Larry Scheer; Tim Gardner; dl-Cougar; dl-Software
		Subject: RE: updating defects=20

		We try to do this, but sometimes it is very difficult to
map a build to a submittal (There were two builds last week and I did
not know whether both of them considered sub12).

		Also we should request QA to update the defects with the
build/submittal information correctly.=20

		_____________________________________________
		From: Larry Scheer
		Sent: Thursday, March 20, 2008 2:24 PM
		To: Tim Gardner; dl-Cougar; dl-Software
		Subject: RE: updating defects=20

		I would like to add that you correctly update the "built
in submittal:" and "of project" fields with the correct submittal and
project the defect is fixed in when you are updating the resolution
page. Some folks are just typing digits in these required fields. This
habit hides the fix from queries on those fields. Clear Quest is hard
enough to use as it is, please don't make it any harder to find
information in its database.

		Thanks,=20

		Larry=20

		_____________________________________________
		From: Tim Gardner
		Sent: Thursday, March 20, 2008 2:09 PM
		To: dl-Cougar; dl-Software
		Subject: updating defects=20


		This is just a freindly reminder to be diligent about
updating clearquest for the defects you are working on.=20

		For any defect you are working on you should be updating
the defect at least on a daily basis.=20

		This is always a good practice but is even more
important as we approach the end of a release.=20

		For lessons in how to update a defect, please see Mike
Lee, the master of the defect update.=20

		Tim=20





------_=_NextPart_001_01C88AFB.7B6B3DB8
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.3790.2706" name=3DGENERATOR></HEAD>
<BODY=20
style=3D"WORD-WRAP: break-word; webkit-nbsp-mode: space; =
webkit-line-break: after-white-space">
<DIV dir=3Dltr align=3Dleft><SPAN class=3D368492802-21032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Because one again some people don't update the =
p4 number=20
field. They just put a . or space in the field.</FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D368492802-21032008><FONT =
face=3DArial=20
color=3D#0000ff size=3D2>Other than this, it may work if we filter the =
changes that=20
were made to the dev branch.</FONT></SPAN></DIV><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> Ian Brown <BR><B>Sent:</B> =
Thursday,=20
  March 20, 2008 6:25 PM<BR><B>To:</B> Tim Gardner<BR><B>Cc:</B> Maxim=20
  Kozlovsky; Larry Scheer; Jobi Ariyamannil; dl-Cougar;=20
  dl-Software<BR><B>Subject:</B> Re: updating =
defects<BR></FONT><BR></DIV>
  <DIV></DIV>Why don't we do this automatically, put your p4 check in =
number=20
  into the bug -- which we do, then just search for every bug with a p4 =
checkin=20
  number between the two submittal p4 numbers -- doesn't that solve the =
problem?
  <DIV><BR class=3Dwebkit-block-placeholder></DIV>
  <DIV><BR>
  <DIV>
  <DIV>On Mar 20, 2008, at 7:17 PM, Tim Gardner wrote:</DIV><BR=20
  class=3DApple-interchange-newline>
  <DIV><!-- Converted from text/rtf format -->
  <P><FONT face=3DArial color=3D#0000ff size=3D2>Max,</FONT> </P>
  <P><FONT face=3DArial color=3D#0000ff size=3D2>Please don't do this. =
Larry has=20
  enough on his plate with his cougar tasks and taking over for =
Ken.</FONT>=20
  <BR><FONT face=3DArial color=3D#0000ff size=3D2>He is also responsible =
for writing=20
  the submittal notes. To do this he relies on the info in clearquest =
being=20
  correct.</FONT> <BR><FONT face=3DArial color=3D#0000ff =
size=3D2>Putting incorrect=20
  info in the defect makes his work harder or causes the submittal notes =
to be=20
  incorrect.</FONT> <BR><FONT face=3DArial color=3D#0000ff size=3D2>If =
you don't want=20
  to take the time to put the correct info in each defect you fix then =
perhaps=20
  you would like to be</FONT> <BR><FONT face=3DArial color=3D#0000ff=20
  size=3D2>responsible for writing the submittal notes. Let me know. I'm =
sure=20
  Larry would glady have you take over this task.</FONT> <BR><FONT =
face=3DArial=20
  color=3D#0000ff size=3D2>I'm sure there is a better way to do this. We =
are open to=20
  suggestions. But at the same time we have very limited</FONT> =
<BR><FONT=20
  face=3DArial color=3D#0000ff size=3D2>resources for this kind of work =
at the=20
  moment.</FONT> </P>
  <P><FONT face=3DArial color=3D#0000ff size=3D2>Tim</FONT> </P><BR>
  <UL>
    <P><FONT face=3DTahoma =
size=3D1>_____________________________________________=20
    </FONT><BR><B><FONT face=3DTahoma size=3D1>From: &nbsp;</FONT></B> =
<FONT=20
    face=3DTahoma size=3D1>Maxim Kozlovsky&nbsp; </FONT><BR><B><FONT =
face=3DTahoma=20
    size=3D1>Sent:&nbsp;&nbsp;</FONT></B> <FONT face=3DTahoma =
size=3D1>Thursday, March=20
    20, 2008 4:02 PM</FONT> <BR><B><FONT face=3DTahoma=20
    size=3D1>To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT face=3DTahoma =
size=3D1>Larry=20
    Scheer; Jobi Ariyamannil; Tim Gardner; dl-Cougar; dl-Software</FONT> =

    <BR><B><FONT face=3DTahoma=20
    =
size=3D1>Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> =
<FONT=20
    face=3DTahoma size=3D1>RE: updating defects</FONT> </P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>Is it a big deal if =
the build in is=20
    off by three? Or by 4? When does the big deal start exactly? Instead =
of=20
    tolerating putting incorrect information in the defect it would be =
much=20
    better for everybody if this information would be updated when the =
submittal=20
    is actually produced. You know the changes you have selected for the =

    submittal. You can find all the defects that have state fixed with =
the=20
    change numbers from this submittal. This produces the list of the =
defects=20
    that have been fixed in the submittal without any guess work and =
without any=20
    possibility of producing incorrect information. </FONT></P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>I am just going to =
continue putting=20
    incorrect information there as a reminder for you that you have to =
fix the=20
    process.</FONT> </P>
    <P><FONT face=3DTahoma=20
    =
size=3D2>_____________________________________________<BR></FONT><B><FONT=
=20
    face=3DTahoma size=3D2>From:</FONT></B><FONT face=3DTahoma size=3D2> =
Larry=20
    Scheer<BR></FONT><B><FONT face=3DTahoma =
size=3D2>Sent:</FONT></B><FONT=20
    face=3DTahoma size=3D2> Thursday, March 20, 2008 3:58 =
PM<BR></FONT><B><FONT=20
    face=3DTahoma size=3D2>To:</FONT></B><FONT face=3DTahoma size=3D2> =
Jobi Ariyamannil;=20
    Tim Gardner; dl-Cougar; dl-Software<BR></FONT><B><FONT face=3DTahoma =

    size=3D2>Subject:</FONT></B><FONT face=3DTahoma size=3D2> RE: =
updating=20
    defects</FONT> </P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>Yes, this is an =
issue. Before I=20
    started doing the submittals I didn&#8217;t know what to put at =
times for the=20
    build so I usually just put what I thought was the next build. As =
long as it=20
    is close and as meaningful, by this I mean not random and at least =
the &#8220;for=20
    project field&#8221; matches the project that you are working =
on.</FONT></P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>My request is for an =
honest=20
    attempt/guess to get it &#8220;right.&#8221;&nbsp; It is no big deal =
if it the &#8220;build=20
    in&#8221; is off by one or two. Tim asked for diligence, I asked for =
a bit more=20
    kindness and awareness when entering the data. We all know were the =
weak=20
    spots and irritations are. We know that it will accept random =
garbage in=20
    many of the fields. I&#8217;m just saying, asking, that people =
don&#8217;t defeat the=20
    intention of the tool just because they can, or feeling grumpy. I =
imagine it=20
    is going to be a while before anyone gets around to fixing the =
defects in=20
    the defect tracking tool.</FONT></P>
    <P><FONT face=3DTahoma=20
    =
size=3D2>_____________________________________________<BR></FONT><B><FONT=
=20
    face=3DTahoma size=3D2>From:</FONT></B><FONT face=3DTahoma size=3D2> =
Jobi=20
    Ariyamannil<BR></FONT><B><FONT face=3DTahoma =
size=3D2>Sent:</FONT></B><FONT=20
    face=3DTahoma size=3D2> Thursday, March 20, 2008 2:46 =
PM<BR></FONT><B><FONT=20
    face=3DTahoma size=3D2>To:</FONT></B><FONT face=3DTahoma size=3D2> =
Larry Scheer; Tim=20
    Gardner; dl-Cougar; dl-Software<BR></FONT><B><FONT face=3DTahoma=20
    size=3D2>Subject:</FONT></B><FONT face=3DTahoma size=3D2> RE: =
updating=20
    defects</FONT> </P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>We try to do this, =
but sometimes it=20
    is very difficult to map a build to a submittal (There were two =
builds last=20
    week and I did not know whether both of them considered =
sub12).</FONT></P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>Also we should =
request QA to update=20
    the defects with the build/submittal information correctly.</FONT> =
</P>
    <P><FONT face=3DTahoma=20
    =
size=3D2>_____________________________________________<BR></FONT><B><FONT=
=20
    face=3DTahoma size=3D2>From:</FONT></B><FONT face=3DTahoma size=3D2> =
Larry=20
    Scheer<BR></FONT><B><FONT face=3DTahoma =
size=3D2>Sent:</FONT></B><FONT=20
    face=3DTahoma size=3D2> Thursday, March 20, 2008 2:24 =
PM<BR></FONT><B><FONT=20
    face=3DTahoma size=3D2>To:</FONT></B><FONT face=3DTahoma size=3D2> =
Tim Gardner;=20
    dl-Cougar; dl-Software<BR></FONT><B><FONT face=3DTahoma=20
    size=3D2>Subject:</FONT></B><FONT face=3DTahoma size=3D2> RE: =
updating=20
    defects</FONT> </P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>I would like to add =
that you=20
    correctly update the &#8220;built in submittal:&#8221; and &#8220;of =
project&#8221; fields with the=20
    correct submittal and project the defect is fixed in when you are =
updating=20
    the resolution page. Some folks are just typing digits in these =
required=20
    fields. This habit hides the fix from queries on those fields. Clear =
Quest=20
    is hard enough to use as it is, please don&#8217;t make it any =
harder to find=20
    information in its database.</FONT></P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>Thanks,</FONT> </P>
    <P><FONT face=3DArial color=3D#000080 size=3D2>Larry</FONT> </P>
    <P><FONT face=3DTahoma=20
    =
size=3D2>_____________________________________________<BR></FONT><B><FONT=
=20
    face=3DTahoma size=3D2>From:</FONT></B><FONT face=3DTahoma size=3D2> =
Tim=20
    Gardner<BR></FONT><B><FONT face=3DTahoma =
size=3D2>Sent:</FONT></B><FONT=20
    face=3DTahoma size=3D2> Thursday, March 20, 2008 2:09 =
PM<BR></FONT><B><FONT=20
    face=3DTahoma size=3D2>To:</FONT></B><FONT face=3DTahoma size=3D2> =
dl-Cougar;=20
    dl-Software<BR></FONT><B><FONT face=3DTahoma =
size=3D2>Subject:</FONT></B><FONT=20
    face=3DTahoma size=3D2> updating defects</FONT> </P><BR>
    <P><FONT face=3DArial size=3D2>This is just a freindly reminder to =
be diligent=20
    about updating clearquest for the defects you are working on.</FONT> =
</P>
    <P><FONT face=3DArial size=3D2>For any defect you are working on you =
should be=20
    updating the defect at least on a daily basis.</FONT> </P>
    <P><FONT face=3DArial size=3D2>This is always a good practice but is =
even more=20
    important as we approach the end of a release.</FONT> </P>
    <P><FONT face=3DArial size=3D2>For lessons in how to update a =
defect, please see=20
    Mike Lee, the master of the defect update.</FONT> </P>
    <P><FONT face=3DArial size=3D2>Tim</FONT>=20
</P><BR><BR></UL></DIV></DIV><BR></DIV></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C88AFB.7B6B3DB8--
