X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C88AF9.BFC077D0@onstor-exch02.onstor.net>; Thu, 20 Mar 2008 19:17:44 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C88AF9.BFC077D0"
Content-class: urn:content-classes:message
Subject: RE: updating defects
Date: Thu, 20 Mar 2008 19:17:44 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E08FC331D@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08FC329E@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: updating defects
Thread-Index: AciKzo5bqx+7gVrvT4OclSfNw5n07gAAEmAwAAEhHVAAAZ3zwAACrx5AAAUTMoA=
From: "Tim Gardner" <tim.gardner@onstor.com>
To: "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_01C88AF9.BFC077D0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Max,

Please don't do this. Larry has enough on his plate with his cougar
tasks and taking over for Ken.
He is also responsible for writing the submittal notes. To do this he
relies on the info in clearquest being correct.
Putting incorrect info in the defect makes his work harder or causes the
submittal notes to be incorrect.
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
responsible for writing the submittal notes. Let me know. I'm sure Larry
would glady have you take over this task.
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
resources for this kind of work at the moment.

Tim


> _____________________________________________=20
> From: 	Maxim Kozlovsky =20
> Sent:	Thursday, March 20, 2008 4:02 PM
> To:	Larry Scheer; Jobi Ariyamannil; Tim Gardner; dl-Cougar;
> dl-Software
> 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
>=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=20
> 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.
>=20
> 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.
>=20
> _____________________________________________
> From: Jobi Ariyamannil=20
> 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).
>=20
> Also we should request QA to update the defects with the
> build/submittal information correctly.
>=20
> _____________________________________________
> From: Larry Scheer=20
> 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.
>=20
> Thanks,
>=20
> Larry
>=20
> _____________________________________________
> From: Tim Gardner=20
> Sent: Thursday, March 20, 2008 2:09 PM
> To: dl-Cougar; dl-Software
> Subject: updating defects
>=20
>=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
>=20
>=20

------_=_NextPart_001_01C88AF9.BFC077D0
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>RE: updating defects</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Max,</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Please don't do this. =
Larry has enough on his plate with his cougar tasks and taking over for =
Ken.</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">He is also =
responsible for writing the submittal notes. To do this he relies on the =
info in clearquest being correct.</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Putting incorrect =
info in the defect makes his work harder or causes the submittal notes =
to be incorrect.</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">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</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">responsible for =
writing the submittal notes. Let me know. I'm sure Larry would glady =
have you take over this task.</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">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</FONT>

<BR><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">resources for this =
kind of work at the moment.</FONT>
</P>

<P><FONT COLOR=3D"#0000FF" SIZE=3D2 FACE=3D"Arial">Tim</FONT>
</P>
<BR>
<UL>
<P><FONT SIZE=3D1 =
FACE=3D"Tahoma">_____________________________________________ </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">From: &nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Maxim Kozlovsky&nbsp; </FONT>

<BR><B><FONT SIZE=3D1 FACE=3D"Tahoma">Sent:&nbsp;&nbsp;</FONT></B> <FONT =
SIZE=3D1 FACE=3D"Tahoma">Thursday, March 20, 2008 4:02 PM</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">To:&nbsp;&nbsp;&nbsp;&nbsp;</FONT></B> <FONT SIZE=3D1 =
FACE=3D"Tahoma">Larry Scheer; Jobi Ariyamannil; Tim Gardner; dl-Cougar; =
dl-Software</FONT>

<BR><B><FONT SIZE=3D1 =
FACE=3D"Tahoma">Subject:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</FONT>=
</B> <FONT SIZE=3D1 FACE=3D"Tahoma">RE: updating defects</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">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. </FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I am just going to =
continue putting incorrect information there as a reminder for you that =
you have to fix the process.</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Larry Scheer<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, March 20, 2008 3:58 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jobi Ariyamannil; Tim Gardner; dl-Cougar; =
dl-Software<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: updating defects</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Yes, this is an =
issue. Before I started doing the submittals I didn&#8217;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 &#8220;for project field&#8221; matches the =
project that you are working on.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">My request is for an =
honest attempt/guess to get it &#8220;right.&#8221;&nbsp; It is no big =
deal if it the &#8220;build in&#8221; 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&#8217;m just saying, asking, that people don&#8217;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.</FONT></P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Jobi Ariyamannil<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, March 20, 2008 2:46 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Larry Scheer; Tim Gardner; dl-Cougar; dl-Software<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: updating defects</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">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).</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Also we should =
request QA to update the defects with the build/submittal information =
correctly.</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Larry Scheer<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, March 20, 2008 2:24 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tim Gardner; dl-Cougar; dl-Software<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> RE: updating defects</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">I would like to add =
that you correctly update the &#8220;built in submittal:&#8221; and =
&#8220;of project&#8221; 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&#8217;t make it any harder to find information in =
its database.</FONT></P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Thanks,</FONT>
</P>

<P><FONT COLOR=3D"#000080" SIZE=3D2 FACE=3D"Arial">Larry</FONT>
</P>

<P><FONT SIZE=3D2 =
FACE=3D"Tahoma">_____________________________________________<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">From:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Tim Gardner<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Sent:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> Thursday, March 20, 2008 2:09 PM<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">To:</FONT></B><FONT SIZE=3D2 =
FACE=3D"Tahoma"> dl-Cougar; dl-Software<BR>
</FONT><B><FONT SIZE=3D2 FACE=3D"Tahoma">Subject:</FONT></B><FONT =
SIZE=3D2 FACE=3D"Tahoma"> updating defects</FONT>
</P>
<BR>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is just a freindly reminder to be =
diligent about updating clearquest for the defects you are working =
on.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">For any defect you are working on you =
should be updating the defect at least on a daily basis.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">This is always a good practice but is =
even more important as we approach the end of a release.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">For lessons in how to update a defect, =
please see Mike Lee, the master of the defect update.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tim</FONT>
</P>
<BR>
<BR>
</UL>
</BODY>
</HTML>
------_=_NextPart_001_01C88AF9.BFC077D0--
