A quick note on the stability of our software and change of our support policy for Joomla! 1.6.
This dire situtation made me think very hard and take a very important business decision.
I will discontinue to provide active support of Joomla! 1.6 across all of my products. What does that mean? No, I'm not going to remove any Joomla! 1.6 related code and, of course, it does not mean that I am not going to pursue compatibility of my products with Joomla! 1.6 and its successors. However, the following issues will be treated as lowest priority issues and will not prompt me to provide an immediate solution:
Please note that major functional issues like restoration of backup archives taken with Akeeba Backup or partial/full loss of functionality when using Admin Tools Professional will still be treated as high priority bugs. These have nothing to do with the ever changing nature of Joomla! 1.6 and will, of course, be treated promptly. If it's a really serious bug, a hotfix package will released as per my usual policy. All of the bugs arising from new or changed APIs in Joomla! 1.6 will be treated as low priority bugs and you will have to wait for a full release cycle before you see any fix, if and only if fixing them does not cause problems with Joomla! 1.5 installations.
If you are wondering why is that, it's because Joomla! 1.6 is still alpha quality. I know it's marketed as stable, however it's anything but. It still has too many bugs and introduces major API changes even in subminor releases. This is not supposed to happen even in beta or release candidate quality software, let alone a stable release. I can't actively support an alpha quality CMS any more. It's hurting my business doing so, because I am forced to either release unstable and untested releases of my software to work around issues with Joomla! 1.6 or suffer a ton of support requests and emails telling me that my software "broke" your site. You know what? In both cases I get a ton of support requests anyway and that hurts my business in so many ways - one major way being that I get to answer support requests where I can't really provide any help instead of improving the software. On top of that, it also makes me look bad, despite the hundreds of hours I've spent trying to tame that beast.
So, there you have it. That's the plan for the rest of 2011. Now I'm going back to coding so that I can get Admin Tools back to its regular, intended, stable condition.
Nicholas K. Dionysopoulos
Lead Developer and owner, AkeebaBackup.com