​For production environments, it's advisable to maintain UNA sites at a stable version. For experimental purposes, you can set up various test sites with different intermediate testing versions. For instance, while UNA's latest stable release is 13.1.0, there are newer versions like 14.0.0-RC4 currently available. However, the latest version isn't necessarily the most suitable for production; although it introduces the newest features, stability is paramount in a production setting. Therefore, it's crucial to use only stable versions in production environments and reserve testing versions for separate development sites.​

Regarding the "modzzz-update" topic, it's important to note that module developers typically update their modules in alignment with stable UNA CMS releases or apply security patches as needed. Given UNA's rapid development pace on GitHub, it would be impractical for module developers to update their modules with every core test version release. Consequently, developers like Modzzz focus on ensuring compatibility with stable core versions of UNA CMS, rather than releasing updates for alpha, beta, or release candidate test versions. This approach is practical, considering the extensive number of modules they manage and the potential for increased support inquiries. Therefore, it's reasonable for developers to prioritize updates that align with stable UNA core versions to maintain compatibility and system stability. As for me, this is how I work: I develop an application that includes submodules. First, I ensure that the core has a stable version; then, I release modules compatible with that stable core version.