That was asked also by a customer two days ago during the
webinar presenting the new features of UltraEdit for Windows/UEStudio v2023.2 which I viewed too. The answer was a problem with signing all files if I remember correct.
It is also typical that UltraEdit, Inc. first makes the installer files for a major upgrade available on their website, and two or three weeks later after all related web pages are updated, publishes a newsletter with information about the new major release and makes the upgrades available via the built-in update/upgrade feature.
That makes it also possible that customers early upgrading via a download of the installer file from the website and manual execution like the beta testers can quickly report a serious problem with the public release version. I reported by email three days ago that UE/UES v2023.2.0.27 has a serious problem with the scripting command
UltraEdit.messageBox() which is simply not opening a message box during script execution in this version while the scripting command works with UE/UES v2023.1.0.23 and former versions.
Many companies have such a publishing strategy for major releases including Microsoft. I upgraded Windows 11 already to 23H2 although not yet available for Windows users in Europe by downloading and installing the Windows 11 upgrade manually from the Microsoft website.
It makes a difference if a customer with a personal license upgrades manually as soon as possible directly from the website or if a company with hundreds or thousands of installations upgrade all via built-in upgrade/update feature. A small delay of a few weeks between offering a major release via direct download on the website and a more or less automatically applied upgrade for thousands or millions of users gives the software producing company a short time to fix serious bugs reported by early upgrading customers before the real rollout of the new major release starts. In other words customers interested in a stable release should better wait a month or two after a new major release is available for download and installation before doing the upgrade. This is a general rule which I observed over the last 25 years for all applications independent on the software producing company.