Hi all, We are please to announced that the 0.2 (Bold Badger) version is ready [?] In fact it's the 0.2.1 because we've got a last bug to solve yesterday [?] You can get it at http://www.shinken-monitoring.org/download/ (only sources from now, we are working in the demo VM)
The changelog of this version is quite long (http://tinyurl.com/35o6chb). We add some great new features and solved a lot of bugs. The major new features are : *new code layout, no more all in src directory :) *easy installation with the setup.py script *Python 2.4 and 2.5 compatibility (for RedHat and Debian users) *Pyro 3 and 4 compatibility :) (for Debian) *new code for notification management. Far more easy to understand and with downtimes and acknowledgment ok :) *clean and helpful sample configuration files (simple server, HA installation and load balancing one) *add a lot of automated regressions and end-to-end tests :) *problem/impacts management for seeing only real problems in real time monitoring *now you can get the tar ball, untar it and launch from every where. Test is even more easy now :) There are more new features as you can see in the Changelog like a max_plugins_output_length parameter or a last_perf_data macro. Thanks to everyone that send us patches, really. You can get the full list in the THANKS file in the sources. Now it's time to take a very small break before the 0.3 to talk about what we all want to do for this project and how we want it to be done. The majors points are : *the global project vision (what we will do and what we will not do) *how to manage the documentation (where to put the doc, how make it easy to manage and edit) *how to prioritize features (feature packs or user value first?) and release speed ("when it's done" or at "fixed dates"?) *some dev rules (will be simples and inherited from project vision in fact) We will discuss about each one in another thread. Some project points are already managed : we want this project to be as open as possible That means we do not want to be dictators that do not listen to others. We started this project, but now it not only ours. That's why we open the git access to other members, and we will do it for every one that sends us good patches and wants to help this project (that means documentation, website or code). From now on we are 6 to have this access : * David Guenault * Gerhard Lausser * Olivier LI-KIANG-CHEONG * Luke L * Jean Gabès * Nicolas Dupeux But the participation is not limited to the code or documentation. If we are doing something wrong, just say it. We will make errors, we are humans [?] and if no one tells us, we will still make some. We really hope this 0.2 version will please everyone and that you will test and hack it a lot. Packagers, we are open to help you on created Shinken package for majors distributions. Olivier already works on a Centos package but it still needs some adaptation (need python2.6 and now 2.4 is OK) to be done. We think this code is stable, and I (Jean) will start to use in my production environment. We still have a long but full of passion road in front of us ( https://sourceforge.net/apps/trac/shinken/report/2). Hopefully, the majors and hard points are already behind us [?] When we will have finished the talk about vision, documentation, features and dev rules in the others threads, we will go even farther in a project that all of us can be proud of it, and the first reason for it is because it's fully open [?] Jean & Gerhard
<<330.gif>>
<<331.gif>>
<<347.gif>>
<<360.gif>>
------------------------------------------------------------------------------ This SF.net Dev2Dev email is sponsored by: Show off your parallel programming skills. Enter the Intel(R) Threading Challenge 2010. http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________ Shinken-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shinken-devel
