About version naming - how I see such

[Kvarkas]

Let me shed some light on this dark matter (about version naming) — just to make sure we’re on the same page. :) So, the versions that are released have a download link on the page, and they are divided into three levels:

"Prod" or "Release" version — I am sure it’s safe to use in any environment, including corporate users (as of the release date). Only important bug fixes will be released for this version. Except then fixes are posible or implemented in next version release.

"RC" (Release Candidate) — It’s safe to use in corporate environments, but it could have some specific bugs or unexpected system behaviors. Therefore, it’s advised to use it mostly in UAT or in PROD with precautions. Active bug fixes will be released for this version.

"Beta" or "Nightly Build" — This is for testing and checking how everything works. It can be used in TEST environments for corporate users, but it may contain some bugs, even security-related ones. However, I believe it won’t do anything completely wrong, though it might be vulnerable under specific conditions. Some bugs may be fixed, while others might be deferred to the next version release (by version, I mean not the build number).

And finally, the "Alpha" or just "NB" (Nightly Build) — this version doesn’t have a link on our app page but is only available from GitHub builds. The intention is to have it automated by GitHub and/or AppVeyor actions after every new commit to the branch (though it’s currently failing, and I’m not sure why). This version is the most dangerous in terms of user data, settings, and possibly configs, as it may contain new code, formats, schemas, methods, or other components required for transitions. It’s only tested for functionality. Its will be "pre-released" in GitHub terms just because they dont have alfa release term, and distributed as archive (no installation package) just for entusiast who want to test but dont want to install VS to make builds themselfs.