In a support discussion titled “Switch from beta to stable releases,” joa asks how to switch from running Discourse beta versions (2.4.0 beta 2/3) to stable releases once available, expressing concern about reverting to an older stable version like 2.3.0. pfaffman advises that most users should run tests-passed — the default — rather than stable, since bug fixes are delivered faster and waiting for stable may delay critical updates by weeks or months. joa questions whether running beta is the norm, expecting stable to be the default for reduced risk. pfaffman clarifies that tests-passed is the recommended path for safety and timeliness. RGJ corrects the notion that stable doesn’t receive bug fixes, noting that stable branches do get patches without new features (thus fewer new bugs). To answer the original “how” question, RGJ instructs: wait for 2.4.0 stable to be released, then edit app.yml, change #version: tests-passed to version: stable (removing the #), and rebuild the app. The consensus leans toward tests-passed for most users, but switching to stable is straightforward when desired.
When I initially installed Discourse I got Discourse 2.4.0 beta 2, I think. Then beta 3.
I’d like to get to the stable releases instead of the beta versions.
I‘m aware that it’s probably not a good idea to go from a 2.4.0 beta „back“ to a stable 2.3.0 version and I assume there is no stable 2.4.0 yet. But once 2.4.0 (stable) is out, how can I switch to it and make sure I’m not prompted to update to a beta but only install stable releases?
Is the expectation that most people will run beta? I’d have expected to want to run stable by default to decrease my risk of running into undiscovered bugs.
The expectation is that most people will run tests-passed, as that is the default. The solution to virtually every bug is to upgrade, and if you’re on beta or stable then it’ll be weeks or months before you can upgrade to the new version. It’s safest to run tests-passed as you’re doing now.
That’s incorrect - bugs are fixed on stable as well: Commits · discourse/discourse · GitHub
And because there are (almost) no new features, there are virtually no new bugs being introduced.
But the question wasn’t if, it was how:
Wait until 2.4.0 is out and then find the line #version: tests-passed in your app.yml , change it to version: stable , and rebuild.
(don’t forget to remove the # as well)