SV: Nagios 2.0 stable

[Andreas Ericsson]

Michael Gaskin wrote:
> Jeff, 
> 
> I care because as a company who sells solutions to corporations, the
> word beta is scary.  While I agree it does appear to work, I also want
> to penetrate markets that may not be a traditional open source
> customer.
> 

As a "solution-vendor", you can't ever dodge the responsibility to test, 
test, test and test the solutions you intend to sell. Also, you should 
get around to doing some testing.

If you're interested in making Nagios stable so you can sell it, you 
should hunt for bugs ferociously and submit patches upstream. It might 
even be worth spending a couple of company bucks on it.

> Bad grammar, sorry...  Need more coffee.
> 
> 
>>>>jeff vier <boinger at tradingtechnologies.com> 3/23/2005 7:05 AM >>>
> 
> On Wed, 2005-03-23 at 11:39 +0100, Bergström Sebastian wrote:
> 
>>I realise that my question is unclear. I'm refering to the fact that
> 
> 2.0 still is in beta. 
> 
>>We are running v.1.2 currently and are interested in the v.2.0.
>>
>>I'm wondering if anyone has an idea of how much time it might take
> 
> before 2.0 can go into a stable (non-beta) state.
> 
>>Any idea?
> 
> 
> To put it bluntly: Who Cares?
> 
> There are so many of us running it in production (I, myself, have been
> doing so since "alpha"), isn't that good enough?
> 
> There will always be bugs, no matter what you call it (alpha, beta,
> pr,
> rc, gold, etc).
> 
> In my, and I'm sure many others', experience, super-pre-double-alpha
> code from a nice community-supported project like this is still going
> to
> have less bugs than anything similar from Microsoft no matter how many
> "final" versions they have.
> 
> And if something major does come up, there's usually a fix/work-around
> in a few hours or days, not weeks or months.
> 
> So, just run it.  If you don't like it, I'll buy you a coke.
> 
> --boinger
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: 2005 Windows Mobile Application
> Contest
> Submit applications for Windows Mobile(tm)-based Pocket PCs or
> Smartphones
> for the chance to win $25,000 and application distribution. Enter today
> at
> http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click 
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
> Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
> Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
> by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op=click
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at 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
> 

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_idh83&alloc_id149&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at 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