On 2014-01-18 18:35, Sven Nierlein wrote:
Hi list,
Due to the recent actions by nagios inc
(https://www.monitoring-plugins.org/news/new-project-name.html), i think its
quite important to do a release as soon as possible to give people a chance to
change. Is anyone aware of real show stoppers? The packages itself are tested
and work quite well (besides some small
issues). Anything else missing for a first release?
Making releases is easy - deciding on what the release means is harder.
I don't want to promise ABI or API stability for the whole tree the way
nagios did. In fact, I'm not too keen on promising any type of
integration point level stability at all above "best effort" or "tell us
if you're interested, and we'll help you fix them if we break them".
The kind of broker module API provided by nagios is insane - if it's not
possible to refactor code without a new major release, you've fucked up.
But we should do a release ASAP, yes.
