On 10/01/2010 12:49 PM, Michael Friedrich wrote:
> Andreas Ericsson wrote:
>>
>> How about "download the proposed fix from CVS and give that a go"?
>>
>
> True for testing environments and source upgrades (if people can do that
> theirselves).
> Untrue for package upgrades and similar upgrade paths.
>
True that. This, btw, is why package maintainers very rarely jump the
guns to get new versions out the door though, so I doubt it affects
anyone who's installed Nagios that way.
> Main problem targets the fact that the error reports differ in various
> ways. Only a developer might get the idea what did change, but if I were
> just an user with daily business I would spend a lot of time checking on
> possible errors. Better having a new release telling this is fixed.
>
>> Since the fix awaits input from testers we can't very well release it
>> immediately. You've tested it, so that makes one person. If a few more
>> report that it's now working as intended without any downsides we'll
>> probably go ahead and cut a release in the next few days, but releasing
>> untested code that might break something else just to fix a bug isn't
>> really good practice.
>>
>
> Well good to hear that, not rushing into releases. Maybe instrumented by
> asking on different channels for testing help (like Twitter and Facebook
> getting very popular right now). Just an idea to make life more easy.
>
Automated testing beats user testing 9 times out of 10. That's why we need
to send all our icecream to Ton for working on adding automated tests to
Nagios.
--
Andreas Ericsson [email protected]
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
Considering the successes of the wars on alcohol, poverty, drugs and
terror, I think we should give some serious thought to declaring war
on peace.
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]