[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ed8d5cd3-ae6e-db9e-fa55-fe5842102a51@users.sourceforge.net>
Date: Tue, 28 Nov 2017 21:18:01 +0100
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Takashi Iwai <tiwai@...e.de>, alsa-devel@...a-project.org
Cc: Arvind Yadav <arvind.yadav.cs@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Sakamoto <o-takashi@...amocchi.jp>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: ALSA: nm256: Fine-tuning for three function implementations
>> Would you like to discuss the circumstances for the one glitch
>> to which you might refer to?
>
> No need for discussion.
I disagree to this view again.
> It's difficult to recover a lost trust.
I can follow this view to some degree.
But I find that the current might point also other weaknesses out
in the general software development process.
> The best way is to show how you don't fall into the same issue any longer,
Your expectations go into lower failure probabilities.
But you might become disappointed again because of human work in general.
> and it essentially means the actual testing of the patches.
I find that corresponding progress depends then also on reasonable
and accepted procedures from trusted test environments.
> Now it's clear why the testing is demanded?
I can follow your desire to some degree.
> There is no other way.
There are more (technical) possibilities to consider where development tools
like a continuous integration system can help.
Regards,
Markus
Powered by blists - more mailing lists