I’d like to run the latest stable version of Discourse, but not install beta versions. Currently, I get an email from my Discourse instance any time there’s a new beta, but that’s not helpful – and there is no email for new stable versions. I tried subscribing to GitHub’s “releases” for the Discourse repo, but there I am getting no email at all (which is of course not your fault, but would have been a way to mitigate this).
Is there any way to configure the built-in update check if Discourse to only take newer stable releases into account? If not, is there any chance this option might be added in the future?
If you’re already on tests-passed you won’t be stable until the next stable release. Note that in some ways tests-passed is more stable than stable as it’s what discourse.org runs, so it’s the best tested.
I was previously hopping from tag to tag. Seems like when built for v2.2.3, Discourse interprets this as looking for beta updates, not stable updates. Not sure if anything can be done about that?
Now I remember why I wasn’t on stable: that one can actually end up not corresponding to a tag, like currently it is one commit ahead of the latest release. Oh well.
Fair. On the other hand, I don’t want to have to update quite so often.
I was looking at this post about using a specific version:
When I look at github I see stable or tests-passed branches (not tags). However I do see a latest-release tag. What’s the difference between stable (branch) and latest-release (tag)?