Joomla 3.10 Status & Release Strategy
As covered a few times already in the magazine and announced in the Developer Portal, Joomla 3.10 will be released together with 4.0 and will then be supported for two years after its initial release.
The release is intended as a bridge for the current Joomla Users who cannot upgrade all sites to Joomla 4 as some extensions may not be ready for Joomla 4 yet. Additionally Extension developers will find it more straightforward to make their extensions compatible with 3.10 and 4.0 at the same time.
With this article here now, I would like to give you an update on the status of the release, as well as provide an high level release strategy that release will follow under my lead.
The basic release strategy is the same that what we always had with all 3.x releases and nothing is changing here massively. But I would say there are a few things that are different from other 3.x releases. So here is a basic comparison of what you can expect and what you can not expect for this release.
What you can expect from this release
- is going to include primarily Bug and Security fixes
- allowed to improve existing functionalities.
- uses code that helps extension devs to build better extensions that run on both 4.x and 3.10
- is accepting code to help guide the user and extension developer through the upgrade process to make sure the upgrade happens more reliably
- is accepting code and improved information on how to upgrade to 4.x
- is having a fixed EOL date 2 years after its initial release.
What you can not expect from this release
Joomla 3.10 is not
- going to get new innovative features;
- going to get massive API changes;
- going to intentionally break B/C in any shape or form;
- expected to raise its any of the minimum requirements.
The reason for the rules is quite simple: Joomla 3.10 is intended to be as stable as possible so you have less to care on 3.x sites but can focus your time on migrating them step by step to Joomla 4.
Current Status of Joomla! 3.10
So what is the current status of 3.10?
Right now 3.10 is in the alpha state and besides the nightly builds gets regular updates usually together with 4.x, as of this writing we have just released 3.10-alpha3 and 4.0-beta5.
In general 3.10 is almost ready and the main focus right now is on improving the Pre Upgrade Checker Build into 3.10.
The things that we are working on right now (as of this writing)
- Geraint Edwards is working on handling extensions that might break the site on upgrade, so help you to have a successful upgrade path.
- As part of the release blockers Richard Farth is working on the NULL Date handling on upgrading to 4.x from 3.10 for entries in the database that have an empty column.
- There is also one follow up PR still open looking to be tested and merged soon.
Other than that, we have no specific 3.10 related issues or PRs, but we are looking into what can or has to be done to improve the upgrade workflow, or to properly fix the Joomla 4 release blockers.
Call for action: Please test Joomla 3.10 and 4.0 now.
I would like to end this post here with a call for action for all of you. No matter what kind of user or developer you are. Please test 3.10 and 4.0 and report issues you find or see to us.
Every issue that you find in your way of using Joomla that is fixed before the release is an issue you have never to deal with when we do the final releases.
That makes Joomla a better, competitive and enjoyable product for you and all of its users. It saves you and your customers time and money you would have to spend on debugging issues, creating workarounds and hot fixes you would then have to deploy as mitigation for that issue on your sites, templates or extensions until we can patch that issue in the next Joomla Update.
So please help us to make Joomla 3.10 and Joomla 4.0 the best release possible by testing the releases out there now and report the issues found now and propose & test patches so we can fix them before the final release is done.
Thanks, Tobias, for recapping the situation with J! 3.10 and we thank you for keeping us informed. As much as I (among others who are less savvy about GitHub as the developers are) am happy to lend my assistance in testing a pre-stable release of J! 3.10, I am not an alpha tester. I made the decision to not be an alpha tester for anything many years ago and I live in blissful ignorance of the intricate technicalities involved in understanding, building, testing and bug-fixing early versions of software particularly when end-user documentation has not yet been written. Being an alpha tester means, in large part, taking responsibility for one's own actions and being prepared to submit to the decisions of others who may not fully appreciate the views or opinions of other alpha testers in arriving at the point when the feature set(s) that these alpha versions will or will not include.
Having made the point about what prevents me from becoming involved in alpha testing, I believe that it's important that the set of features that will go into J! 3.10 needs to be well defined and locked in place so that beta testing can commence as soon as possible. The Project Roadmap does not indicate a likely timeframe for when this will occur. I agree that roadmaps are not prescriptive and they're subject to change but it would help if we had some ambition. Without knowing anything much about what's happening behind-the-scenes, would it be ambitious to suggest that J! 3.10 beta will be ready for testing around April 2021? Perhaps then we could anticipate an RC version within two months from that, aiming for a stable release of J! 3.10 around Q3 of 2021.
i'm sorry that it took that long to get back to you, i thought I would get a mail on new comments but I did not First of all thank you for your comment and I'm happy to answer your questions.
> I made the decision to not be an alpha tester for anything many years ago and I live in blissful ignorance of the intricate technicalities involved in understanding, building, testing and bug-fixing early versions of software particularly when end-user documentation has not yet been written.
As for why 3.10 is alpha, this has no technical reason as 3.10.0-alpha is as stable as any other 3.9.x version right now. The only reason we choose to release a alpha is to follow "Semantic Versioning". As mention above we are still working on the pre upgrade checker and some migration stuff, that means technically we are not 100% feature complete and there for alpha and not beta. All other parts other than the mention places we improved in 3.10 are 1:1 with 3.9. I can understand why you dont want to be alpha tester I just want to make that clear here
In case of documention the people on docs already have created a few sites regarding 3.10 but as mention above most is 1:1 with 3.9. Do you have anything particular that you miss and we should document for 3.10?
> Being an alpha tester means, in large part, taking responsibility for one's own actions and being prepared to submit to the decisions of others who may not fully appreciate the views or opinions of other alpha testers in arriving at the point when the feature set(s) that these alpha versions will or will not include.
While that can be true in general in this case here I would love to hear any opionions from outside. It seems for some reasone that there is are just very few testing or the masses are just not reporting back thiere results with 3.10. But that is an very important step in the process. You are the people that we build the CMS for so please give us feedback on that, before the release so we can make it as good as possible to start with it. And I can not stress that egnoth any kind of constructive and positive feedback is welcome and will be reviewed by me, up until now I have also repied to all messages that came to me. (Just send me an mail at tobias.zulauf[at]community.joomla.org)
> Having made the point about what prevents me from becoming involved in alpha testing, I believe that it's important that the set of features that will go into J! 3.10 needs to be well defined and locked in place so that beta testing can commence as soon as possible.
Agree the set of features is well defined and we are nearly ready to be feature complete for 3.10.0 once that is done we can move to beta.
> The Project Roadmap does not indicate a likely timeframe for when this will occur.
Yes thats because 3.10.0 will release once 4.0 will be released. We made good progress on 4 recently but there are no finalised timeframe on 4.0 and for that release so also not on 3.10. Please be assured that once there are concrete plans they will be pushlished to the community.
> Without knowing anything much about what's happening behind-the-scenes, would it be ambitious to suggest that J! 3.10 beta will be ready for testing around April 2021? Perhaps then we could anticipate an RC version within two months from that, aiming for a stable release of J! 3.10 around Q3 of 2021.
I can assured you there is nothing particular "happening behind-the-scenes" all what is happening is on GitHub and the general status is regulary reported with the reports of the production department (https://volunteers.joomla.org/departments/production).
As for timing the thing mention above appies we want 3.10 to be released together with 4.0 so we have to await the release timeframe of 4.x and once we have something there it will be published to the community.
I hope that clears your questions and I'm sorry for not replying earlier.
By accepting you will be accessing a service provided by a third-party external to https://magazine.joomla.org/