Hi  @arrmo 

Thanks for posting here. Here is an explanation:

Root Cause: Channel Separation and Different Target Users

Different Channel Nature:

• Community Trial Version: This is an earlier, more developer and tech enthusiast-oriented testing channel. It is released early to gather feedback across diverse environments (especially in special or edge-case scenarios), and thus may have some known minor issues. It is not suitable for automatic push through the Controller intended for all users.
• Controller RC Version: This is a “Release Candidate” version very close to the final stable release. It has passed internal testing and the Community Trial filter, achieving high quality with almost no issues. Its goal is to conduct final-stage stability and compatibility validation.

Risk Control and User Experience: If these pre-release versions were pushed directly to all users via the Controller WebUI, many general users unfamiliar with testing procedures might unintentionally upgrade and potentially encounter “minor issues” in the Community Trial version. This would create unnecessary technical support burdens and a poor user experience.

The manual download method sets a “threshold,” ensuring that only users who actively seek out and are willing to accept some risk will obtain these versions. This aligns with standard practices for distributing test software.

Additionally, the community trial version provides a platform for everyone to participate in discussions.