[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: issue verification
From: |
Phil Holmes |
Subject: |
Re: issue verification |
Date: |
Fri, 18 Sep 2020 10:15:03 +0100 |
I don't know if this isn't clear, but just to state the original point of
verifying issues.
If the change is claimed to fix a bug, we compile the previously buggy code
with the release in which the bug is claimed fixed and check that the bug is
no longer there. It it has really disappeared, we change the status of the
issue from Fixed to Verified. i.e. we are certain that the bug is no longer
there.
If the change is to provide updated functionality, then it can be really
quite hard to verify the new functionality, and in any case the patch review
system should do that. So we simply check the patch was pushed into the
claimed build. If it's clear that it was, we mark the status as Verified.
That was the original intention of verifying issues.
--
Phil Holmes
----- Original Message -----
From: "Jonas Hahnfeld" <hahnjo@hahnjo.de>
To: "Michael Käppler" <xmichael-k@web.de>; "Jean Abou Samra"
<jean@abou-samra.fr>; "lilypond-devel" <lilypond-devel@gnu.org>
Sent: Friday, September 18, 2020 7:57 AM
Subject: Re: issue verification
- Re: issue verification, (continued)
- Re: issue verification, Michael Käppler, 2020/09/17
- Re: issue verification, Michael Käppler, 2020/09/17
- Re: issue verification, Michael Käppler, 2020/09/17
- Re: issue verification, Jonas Hahnfeld, 2020/09/18
- Re: issue verification, Michael Käppler, 2020/09/18
- Re: issue verification,
Phil Holmes <=
- Re: issue verification, Michael Käppler, 2020/09/18
- Re: issue verification, Michael Käppler, 2020/09/18
- Re: issue verification, Federico Bruni, 2020/09/18
- Re: issue verification, Jean Abou Samra, 2020/09/18
- Re: issue verification, Michael Käppler, 2020/09/21
- Re: issue verification, Jean Abou Samra, 2020/09/25