Sorry, but have to comment - it was a very poor and inappropriate decision to move all the Tiki sites to Tiki 22.
There are other users to think about than yourselves.
Sure, you want to 'force' everyone to be a tester, however not everyone wants to (or has the time).
But more importantly, by updating all the Tiki 22 and 23 (which are for Testing and Experimental environments only, not production) you are demonstrating to the world the new development issues with Tiki - not the best 'foot' to put forward in a very competitive digital CMS / EMS segment.
Yes, every single piece of software from any organization that is updated will have new bugs. issues, etc., so it is completely understandable that TIki is no exception. This is a normal part of improvement. But, IMO, having first time, or 'sometime' users (on the edge of making a decision about using/deploying a product) experience 'Testing / Experimental' versions is not a wise decision.
Additionally, I believe the majority of serious production environments deploy LTS versions, not STS's, making it much more logical to leave all main Tiki sites on an LTS specifically to get feedback and information about the latest LTS (from both end users and Tiki Admins, who regularly use the Tiki sites).
Yes, keeping up, and even leading, is important, in an ever increasingly competitive
software 'digital app' environment.
But in the absence of 100,000+ paid employees (e.g. MS, Apple, etc.), a solid, stable and polished product will not be in the form of the latest and greatest bleeding edge STS but from focusing on making the current LTS the best it can be.