I am !! In a production environment we may avoid bugs and more risky problems (like an insane SNMP discoverer, or something like that).

So I'll be interested in a stable branch, regularly updated :-)

I think the most important things are :

1) Stability

2) "Silence" - in terms of not talking too much on the network

3) Performance

4) Without less information or functionality than the latest updates

Regards,

Adrien BERTRAND Administrateur Sécurité du Système d'Information

Tel : 01.42.79.47.81 Interne : 5.47.81 [Description : Q_BPCE_Assurances.jpg]

**************************************************************************

From: Tom Laermans <tom.laermans@powersource.cxmailto:tom.laermans@powersource.cx>

To: observium@observium.orgmailto:observium@observium.org

Subject: Re: [Observium] Stable vs Trunk

Message-ID: <528A414B.5040501@powersource.cxmailto:528A414B.5040501@powersource.cx>

Content-Type: text/plain; charset=ISO-8859-1; format=flowed

Hi,

As it turns out, waiting for a bit of software to feel un-buggy enough

to call stable is a little bit like chasing a magic dragon in a

pharmaceutically-enhanced dream, a largely unattainable goal. It's a

little difficult to gauge stability when we have half a dozen commits

per day!

Are any of you using the stable branch, and if so, how often and under

what conditions would you want me to merge changes?

Nobody interested in the stable branch?

Tom