What versioning scheme is used by StreamFX? Stable builds have passed all important tests and should be ready for Production or Live environments. These releases will have a version number containing the letter `c`.Īll promises of warranty or functionality are void. Some bugs and crashes should be expected. Release Candidates are potential Stable releases which still need some testing, but may be used in Production or Live environments. These releases will have a version number containing the letter `b`. They should be avoided in Production or Live enviroments. These releases will have a version number containing the letter `a`.Īll promises of support, warranty or functionality are void.īetas are more stable than Alphas, but may contain the same amount of bugs and crashes. Bugs, Crashes, Freezes, Corruptions, etc should all be fully expected when using these. They contain the latest changes of any kind, and may include an unusual amount of problems. What release type / update channel should I use? TypeĪlphas are as unstable as things can get, and should be avoided at all cost in Production or Live enviroments. While there are no set plans for features, mimicking an agile workflow, most of the time certain features end up being the core of a version. Release Cycle What is the release process for StreamFX?Īll releases will go through the Alpha, Beta, Candidate and Stable phases, depending on their measured or guessed stability. There are a number of questions that are so frequent that they've received their own commands on Discord, so this page is to lessen the use of those commands in the hope that someone will actually read this.
0 kommentar(er)
