About version naming - how I see such #2684
Kvarkas
started this conversation in
Show and tell
Replies: 1 comment 1 reply
-
|
Except you have Nightly Build listed twice, which is it, Alpha or Beta? |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Let me shed some light on this dark matter of version naming — just to make sure we’re on the same page. 🙂
The versions available for download are divided into three levels:
“Prod” / “Release”
This version is fully stable and safe to use in any environment, including corporate users (as of the release date).
Only important bug fixes will be released for this version, unless a fix is only possible or already implemented in the next version.
“RC” (Release Candidate) / “Beta”
This version is generally safe for corporate environments, but it may contain specific bugs or unexpected system behaviours.
It is recommended for UAT or for production use with precautions. Active bug fixes will be released for this version.
It is also suitable for testing and verifying how everything works. It can be used in TEST environments for corporate users, but it may contain bugs — including potential security‑related ones. I don’t expect it to cause anything catastrophic, but it may be vulnerable under certain conditions. Some bugs will be fixed, while others may be deferred to the next version release (by “version,” I mean the major/minor version, not the build number).
“Alpha” / “NB” (Nightly Build)
This version does not appear on the app’s download page and is only available from GitHub builds.
The intention is for GitHub to generate it automatically after every new commit to the branch (though this is currently failing, and I’m not sure why).
This is the most dangerous version in terms of user data, settings, and configuration integrity, as it may contain new code, formats, schemas, methods, or other components required for transitions.
It is tested only for basic functionality.
It will be marked as a “pre‑release” on GitHub simply because GitHub doesn’t have an “alpha” category.
It is distributed as an archive (no installation package) for enthusiasts who want to test it but don’t want to install Visual Studio to build it themselves.
Beta Was this translation helpful? Give feedback.
All reactions