Grandmaster LxCenter Core Team Member LxCenter Representative
Demiurgo - I agree with this philosophy. I believe that priority should go to bug and security fixes and that there shouldn't be any bug or security issues open with new features being implemented. This is an open source project of volunteers that each have their strengths and focus/philosophy of how to move this project forwards. I think your post is a general question, but is there a specific bug you are speaking of?
I think different packages that make up Kloxo should only be updated through the specific action "Update" to change the server mode triggers many actions (eg change permissions) when you only want to Update.
I still think it is right to create patches with critical updates instead of waiting for the release.
mustafaramadhan Messages: 5731 Registered: December 2010 Location: Yogyakarta
Super Grandmaster Forum Moderator
My personal work on 6.1.7 also make 3 scripts related to kloxo install, namely kloxo-installer (replace for old installer: kloxo-install-master and kloxo-install-slave), kloxo-packer (maka local-copy of kloxo components) and kloxo-patcher (like service-pack work on windows os).
So, with kloxo-patcher, possible patch kloxo's code without waiting next release. Say it, for something like critical security issue.
With kloxo-installer (combine with kloxo-packer) possible to install old version and also reinstall.
..:: MRatWork ::..
Server/Web-integrator - perfect not always more useful
--- Need KVM/OpenVZ VPS? - click here (Kloxo-MR READY!) ---