Re: Verification of bug fixes

--047d7b873a105a4b3a04e838624b
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Thanks again, Jirka!

On Tue, Oct 8, 2013 at 5:40 AM, Ji=C5=99=C3=AD Kovalsk=C3=BD <jiri.kovalsky=
@oracle.com>wrote:

>
>  The bug reports were marked as REOPENED because of failing tests;
>>
>
> None of the two bugs was REOPENED. Both were filed as NEW, then FIXED and
> then VERIFIED.


Sorry, I meant to write "... were NOT marked as REOPENED...".


>  instead, they were reported because of them. If a failing test can be
>> linked to a bad bug fix, what's the procedure? (a) the bug reported
>> reopened, or (b) a new bug report is created?
>>
>
> I don't think we track anything like that. It would be too expensive.
>

Ok, it makes sense.

Thanks again for your time. I'm going to summarize all the info you gave me
and send it back to you, similar to what I've done with Mozilla:
http://rodrigorgs.github.io/blog/2013/09/08/mozilla-process/

[]s
Rodrigo

--047d7b873a105a4b3a04e838624b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks again, Jirka!<div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">On Tue, Oct 8, 2013 at 5:40 AM, Ji=C5=99=C3=AD Ko=
valsk=C3=BD <span dir=3D"ltr">&lt;<a href=3D"mailto:[email protected]=
m" target=3D"_blank">[email protected]</a>&gt;</span> wrote:<div cla=
ss=3D"gmail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div class=3D"im">
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
The bug reports were marked as REOPENED because of failing tests;<br>
</blockquote>
<br></div>
None of the two bugs was REOPENED. Both were filed as NEW, then FIXED and t=
hen VERIFIED.</blockquote><div><br></div><div style>Sorry, I meant to write=
 &quot;... were NOT marked as REOPENED...&quot;.=C2=A0</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid=
;padding-left:1ex">

<div class=3D"im">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">
instead, they were reported because of them. If a failing test can be<br>
linked to a bad bug fix, what&#39;s the procedure? (a) the bug reported<br>
reopened, or (b) a new bug report is created?<br>
</blockquote>
<br></div>
I don&#39;t think we track anything like that. It would be too expensive.<b=
r></blockquote><div><br></div><div style>Ok, it makes sense.</div><div><br>=
</div><div style>Thanks again for your time. I&#39;m going to summarize all=
 the info you gave me and send it back to you, similar to what I&#39;ve don=
e with Mozilla:=C2=A0<a href=3D"http://rodrigorgs.github.io/blog/2013/09/08=
/mozilla-process/">http://rodrigorgs.github.io/blog/2013/09/08/mozilla-proc=
ess/</a></div>

<div><br></div><div style>[]s</div><div style>Rodrigo=C2=A0</div></div></di=
v></div>

--047d7b873a105a4b3a04e838624b--