Re: Avoiding conditioning ignorance towards AutoQA

2011-05-03 Thread Tim Niemueller
On 28.04.2011 18:59, Tim Flink wrote: > On 04/28/2011 02:00 AM, Kamil Paral wrote: >>> Keeping the current way will just make me (and possibly others) >>> add filters to throw away messages from AutoQA. Please be aware of >>> how much contributor time you waste by making them hope through >>> usele

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-28 Thread Tim Flink
On 04/28/2011 02:00 AM, Kamil Paral wrote: >> Keeping the current way will just make me (and possibly others) >> add filters to throw away messages from AutoQA. Please be aware of >> how much contributor time you waste by making them hope through >> useless (because the tests have passed and no inf

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-28 Thread Kamil Paral
> Keeping the current way will just make me (and possibly others) add > filters to throw away messages from AutoQA. Please be aware of how > much > contributor time you waste by making them hope through useless > (because > the tests have passed and no information is gained) mails. I realize > you

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-27 Thread Tim Flink
On 04/27/2011 03:00 PM, James Laska wrote: > On Wed, 2011-04-27 at 21:03 +0200, Tim Niemueller wrote: >> On 27.04.2011 15:38, Kamil Paral wrote: - Post only errors It is common, for example, in automated build or continuous integration systems to send out emails only on errors.

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-27 Thread James Laska
On Wed, 2011-04-27 at 21:03 +0200, Tim Niemueller wrote: > On 27.04.2011 15:38, Kamil Paral wrote: > >> > >> - Post only errors It is common, for example, in automated build or > >> continuous integration systems to send out emails only on errors. > >> Similar goes for Unix tools, which tend to be

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-27 Thread Tim Niemueller
On 27.04.2011 15:38, Kamil Paral wrote: >> >> - Post only errors It is common, for example, in automated build or >> continuous integration systems to send out emails only on errors. >> Similar goes for Unix tools, which tend to be quiet if everything >> is ok, and only bother you with output if s

Re: Avoiding conditioning ignorance towards AutoQA

2011-04-27 Thread Kamil Paral
> Hi fellow Fedorans. > > Recently, AutoQA has been introduced to catch typical problems early > in > the update process. In general, I appreciate that effort, but > currently > I find myself in a phase of conditioning ignorance towards AutoQA, > essentially because it is drowning me in irrelevant

Avoiding conditioning ignorance towards AutoQA

2011-04-27 Thread Tim Niemueller
Hi fellow Fedorans. Recently, AutoQA has been introduced to catch typical problems early in the update process. In general, I appreciate that effort, but currently I find myself in a phase of conditioning ignorance towards AutoQA, essentially because it is drowning me in irrelevant information. Th