We have now released the Alpha 2 version of the new 3.7 release. We moved the date a week to include some more features and now we think we have all features merged. That doesn’t mean that all is perfectly running. There are issues to fix and we need a lot more testing. But we are thinking that the state is good enough that we can publish the version and ask for help in testing.
With the “Custom Fields” feature we had a good experience in merging it into a release early. Having it published and available for a larger group of people speeds up the process of making a feature better and solid.
Joomla! 3.6.5 is now available. This is a security release for the 3.x series of Joomla! which addresses three security vulnerabilities, miscellaneous security hardening and three bug fixes; no further changes have been made compared to the Joomla! 3.6.4 release. We strongly recommend that you update your sites.
What’s in 3.6.5
Version 3.6.5 is released to address three security issues, miscellaneous security hardening and three bugs.
Security Issues Fixed
High Priority – Core – Elevated Privileges (affecting Joomla! 1.6.0 through 3.6.4) More information »
Low Priority – Core – Shell Upload (affecting Joomla! 3.0.0 through 3.6.4) More information »
Low Priority – Core – Information Disclosure (affecting Joomla! 3.0.0 through 3.6.4) More information »
Over the last weeks we have sent mixed messages about Joomla! 3.7 and what will be included in the final version. Without having an alpha/beta version published this is always complicated but with this post we are trying to clear the air.
Let us start with an organizational change, because of personal reasons we had to change the release lead for 3.7 and we have set Robert Deutz (CMS maintainer and former PLT member) as the 3.7 Release Lead. He will work closely with PLT and the other teams to get 3.7 out of the door.
We have also set up a schedule for the release, as always this depends on availability of volunteers and the support of the community but the plan is not so challenging so we believe it is achievable.
20th December 2016
10th January 2017
24th January 2017
7th February 2017
Release Candidate 1:
21st February 2017
Release Candidate 2:
7th March 2017
Release Candidate 3:
14th March 2017
Release Candidate 4:
21st March 2017
28th March 2017
As you can see we are starting a bit slowly but increasing the speed over the process. If you are an extension/template developer you should reserve some time at the beginning of March 2017 to test your extensions/templates.
Last but not least, what are the new features we are planning to ship with 3.7? As it looks now there will be three big features beside a lot of minor improvements:
Routing, finally we will have the possibility to use a new routing strategy. It will be an option and you can enable it per component, so you can mix the old and new strategy. If you are using an old extension that does not support the new routing then everything will still work as before.
Custom fields, this is now merged into the staging branch (that’s the branch of Joomla! we are normally using for development) and we are working on bugs and the final integration. There are also some architectural problems to solve but it looks quite good and we are not facing any really big problems.
Associations Manager, this is a Google Summer of Code project we are planning to merge soon. Here we have also an architectural problems to solve, but we know how and we only need some time to do the coding.
Beside these bigger changes we have visually updated the backend template, improved the usability and as already said a lot of minor enhancements.
Please follow the development on Github at https://github.com/joomla/joomla-cms and if you have time to test a feature please do it. The more people testing the better will be the quality of 3.7.0 on release day.
As part of our post-release review process for the 3.6.4 release, the Joomla! Security Strike Team has identified and confirmed an additional side effect of the issue resolved in security advisory 20161002 (CVE-2016-8869) and as such we have revised our assessment of this issue.