Current development plans

[Henrik Stoerner]

It seems version 4.0 has reached some stability - there are still a few
odd bug reports, but nothing that looks like major problems. So I
thought it would be worthwhile to let you know what my plans are.

First, I'm currently pretty busy with other stuff so questions raised
here are not being answered as quickly as I'd like to. Rest assured that
they have not been forgotten, and I will look at all of the reports and
questions - but probably not very much for the next week or so.


I'm currently working on a 4.0.5 release which will be a performance-
improvement release. The current Hobbit code has a flaw in the alert-
module, that makes it use much more CPU time than it should - especially
if you have a large number of statuses that are in an alert state, but
which do not have any recipients defined in hobbit-alerts.cfg. This will
be released sometime in June.

But summer is upon us, and that means less development activity - so
things will slow down as the temperature rises. So don't expect a lot
of activity during the summer.


When I pick up speed again, I haven't yet decided if I should go for
the alert/acknowledge improvements that I've talked about for some 
time, or if I should tackle the issue of a Hobbit client and get that
into a reasonable shape for the more common platforms. I have some ideas
for a rather different client architecture than the current one, and
the client is also *the* missing piece of the whole Hobbit puzzle - so
I could be tempted to get that done. I'd like some feedback on what
you find most urgent.


Regards,
Henrik