Hi Michael, 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. Stay safe Tobias