Following the release of Joomla! 1.0.14 [Daybreak] and Joomla! 1.5.1 [Seenu] we are entering the planning phase for the next minor release of Joomla!: version 1.6. With the release, we have two goals: better planning and more involvement with the community.
We will be determining the goals of the release with a planning process that means that we will determine what we are going to implement before we actually start developing. The focus on community involvement will mean that everyone can give input on the features that might get into the next minor release of Joomla!
So what is the plan?
We are starting our work on Joomla! 1.6 by formally setting the goals for the release. To work out what those goals are going to be we are going to consult with the community.
Following on from the release of Joomla! 1.5.1 [Seenu], we are pleased to announce the immediate release of Joomla! 1.0.14 [Daybreak]. This version has been triggered by reported cross site scripting problems that could occur under the right circumstances. We have also addressed many other general bugs and problems as well.
This release addresses serious security vulnerabilities and you should proceed with testing on a backup copy of your site. Once you have verified that your site works as expected, we recommend upgrade your live site as soon as possible.
The Joomla! community is pleased to announce the immediate availability of Joomla! 1.5.1 [Seenu]. Since the stable release of Joomla! 1.5 we have seen huge numbers of downloads which has helped to push the total number of downloads to over 3 million in less than a year.
We have found in one of the new features of Joomla! 1.5, an XML-RPC Blogger API plugin, a high priority security vulnerability. While this feature is disabled by default on every Joomla! 1.5 install and would have to be manually enabled for the vulnerability to exist, we strongly recommend that all Joomla! 1.5 users upgrade to Joomla! 1.5.1.
Thanks to the work done by both the Joomla! Bug Squad as well as the Development Team , not only has this vulnerability been patched but so have several other smaller issues.