Hello My discourse site is running version v2.2.0.beta5 +24 and I want to get it onto the non-beta of 2.3. Though the upgrade panel on my site looks like it’s trying to grab the 2.4 beta. Is there a way to retarget the update at 2.3 release? Maybe I need directions to do this in Docker instead of the admin panel? Thanks

tests-passed (latest beta) is the default version for all installs. Migrating to stable takes some doing in your container config yml on the server you’re running. If you’re up to the task, there is a line like the following: samples/standalone.yml master db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override #db_shared_buffers: "256MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LC_ALL: en_US.UTF-8 LANG: en_US.UTF-8 LANGUAGE: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override #UNICORN_WORKERS: 3 You’ll need to uncomment that (delete the #), change “tests-passed” to “stable” and rebuild.

It’s generally not recommended that you run on “stable” in spite of its name. It probably won’t hurt, at least for a while, to be on Stable, but it’s likely to cause problems.

Ah if you advise against it then I will heed that advice. We’re not a feature-needy group, a bunch of cyclists operate our team communications in Discourse. We’re happy to sit tight locked on our version for now but I was assuming that 2.3 was “stable” and potentially a better place for us to lock to as opposed to an old beta build.

It’s stable indeed, just as stable as the version 2.2 where you’re in. The issue is that if there’s any security update, you won’t get it as expedited as possible. That’s really most of the issue. Discourse handles something like: master → test-pased → stable. Being test-pased the most stable and updated version of Discourse (that’s why it’s the default option). It’s your choice to go to 2.4 (test-pased) or stay at 2.3 (stable).

[image] marianord: Discourse handles something like: That’s pretty close @marianord. Just add beta between tests-passed and stable and you’ve got it. I would add that I wouldn’t necessarily agree that tests-passed is the most stable - Discourse is a fast moving piece of software, there’ll always be bugs - I’d say any bugs on it get fixed pretty quickly, and you can update to the latest tests-passed release any time to pull in the fixes. @Json_Blob, stable is “stable” in the sense that it does not get updated very frequently. While we do our best to iron out bugs before each of our major releases, we can’t guarantee we’ve found all of them. So stable means that any bugs you have will be there until the next major release, but you can also trust that new bugs will not be introduced for many months. See the second half of my post below for more details on each of our branches. [image] Updates always come before release notes thought_balloonSite feedback This post was last updated 2021-06-28T04:00:00Z (UTC) to detail the current processes. Hi everyone! Multiple topics to address here, let me see if I can cover them all. This is an intentional decision on our end. We don’t have a formal release system for our beta releases. We put out a new release when it makes sense for us to do so. As such, there is generally little warning before a release, and thus not a lot of time to write up release notes. @codinghorror decided it did not make sense …

That makes more sense, ok, so it sounds like the advised path forward if my group decides to take an update is to get onto the “tests-passed” branch and off beta. Is that summation correct? In which case I follow Jeff’s instructions above for the YML adjustment

You’re already in the test-passed branch, as it’s the default one when installing. But your version will keep looking something like v2.4.0.beta1

OH ok i was unclear then, I thought since my build had “beta” in the version I was on the beta branch. Got you.

[image] marianord: The issue is that if there’s any security update, you won’t get it as expedited as possible. That’s incorrect, the team does a great job in cherry picking all security issues into stable.

Even if there’s a new security update between versions? As it happened between 2.2 and 2.3?

Upgrade 2.2 beta to 2.3 release, not 2.4 beta

Product Support Self-hosting

RGJ (Richard - Communiteq) June 19, 2019, 10:03pm 10

That’s incorrect, the team does a great job in cherry picking all security issues into stable.

Topic		Replies	Views
Stable Release Channel Product Support	6	2522	June 17, 2020
Is now the best time to upgrade to a stable release? Product Support	10	1026	January 12, 2023
Switching to non-beta updates only Self-hosting	3	1785	August 20, 2017
Switch from beta to stable releases Product Support	4	3124	September 5, 2019
When should I switch from beta release to stable release? Product Support	6	2756	August 27, 2018

Upgrade 2.2 beta to 2.3 release, not 2.4 beta

Related topics