Hi Alex,
Le 19/01/2016 15:54, Alexander Thurgood a écrit :
> Le 19/01/2016 14:01, Jochen Schiffers a écrit :
>
> Hi Jochen,
>
>> It is IHMO correct (all 6 months) to check if bugreports are actual.
>> The problem is that only one (and occasionally two) devs actually is/are
>> working on the
Hi Alex,
> I've always had a problem with bulk email bug reminders, and this has
> definitely pushed my patience over my limit - for me, it only makes
> sense if one understands the context behind the number of bugs reported
> and tailors the reminder policy accordingly. I accept that we may not
Hi Alex,
my two cents.
It is IHMO correct (all 6 months) to check if bugreports are actual.
The problem is that only one (and occasionally two) devs actually is/are
working on the code. But this not the problem of QA.
Why are you confess? The procedure of QA is another problem than the
Hi Alex,
I understand you und I agree with you in nearly all points.
Am 19.01.2016 um 15:54 schrieb Alexander Thurgood:
I've always had a problem with bulk email bug reminders
+
... receiving 200 or so emails in the process
IMO we have to accept this.
The solution may be a special way für
Le 19/01/2016 14:01, Jochen Schiffers a écrit :
Hi Jochen,
> It is IHMO correct (all 6 months) to check if bugreports are actual.
> The problem is that only one (and occasionally two) devs actually is/are
> working on the code. But this not the problem of QA.
I never said it was the problem of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hy Alex,
>
> I never said it was the problem of QA that only 2 devs work on the
> Base code. My issue is with what appears to have been targeting a
> module for which the number of open bugs will necessarily not have
> diminished a great deal since
