Following the release of Joomla 4.0 Alpha 3, the Joomla 4 Working Group has published below a status update on the anticipated release of Joomla 4.
Overall, a lot of work has gone into Alpha 3, and there is still more work to be done. We are now focusing on the following three main features, which are our release blockers and must be completed before we can go live into Beta phase.
A completed-work estimate for each feature is included with the feature list.
The most up-to-date information regarding the Joomla 4 timeline can be found in our project roadmap.
Following a new proposal last year, the Backend Team has started to work on implementing it. To help with this please look at the backend template repository in https://github.com/joomla/40-backend-template. Most views have had a basic conversion to the new design, however there is a lot of work to be done to fully meet the requirements of the invision prototype.Approx. 70% done.
There has been architecture work carried out on the setup of extensions and provision of services (not web services). com_content is almost migrated, there is only a pr not merged yet which turns the router access into a service. The rest of the core extensions will then be done step by step.Approx. 95% done.
In order to increase security in our code base, the database library now requires prepared statement support. You can find more information about prepared statements at Wikipedia.
The Joomla Security Strike Team got together on 13 May for a code sprint to finish this task. More information about the sprint can be found in our magazine. We’d like to request PostgreSQL users to help test the PDO library that we will be implementing in Joomla 3.9 (and will be the only Postgres available driver in Joomla 4).Work is now ongoing to implement prepared statements into as much as the CMS as possible.Approx. 10% done.
If you want to be part of the Joomla 4 Working Group and help the Joomla 4 Development Team, apply for a role via the Volunteers portal here or feel free to help on an issue on the Issue Tracker.