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. 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. Kind regards, Michael -- DI (FH) Michael Friedrich Vienna University Computer Center Universitaetsstrasse 7 A-1010 Vienna, Austria email: michael.friedr...@univie.ac.at phone: +43 1 4277 14359 fax: +43 1 4277 14279 web: http://www.univie.ac.at/zid Icinga Core& IDOUtils Developer http://www.icinga.org ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Nagios-users mailing list Nagios-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nagios-users ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null