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: [email protected]
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
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]