### Author:  [@Json\_Blob](https://meta.discourse.org/u/Json_Blob)
#### Post date: [19. Juni 2019 um 20:10 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/1 "2019-06-19T20:10:06Z")
Hallo
Meine Discourse-Seite läuft mit der Version v2.2.0.beta5 +24, und ich möchte sie auf die Nicht-Beta-Version 2.3 aktualisieren. Obwohl das Upgrade-Panel auf meiner Seite so aussieht, als würde es versuchen, das 2.4-Beta-Update herunterzuladen. Gibt es eine Möglichkeit, das Update auf die 2.3-Release-Version umzuleiten? Vielleicht benötige ich Anweisungen, um dies in Docker statt über das Admin-Panel durchzuführen?
Vielen Dank
---
### Author:  [@featheredtoast](https://meta.discourse.org/u/featheredtoast)
#### Post date: [19. Juni 2019 um 20:46 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/2 "2019-06-19T20:46:54Z")
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:
>
You’ll need to uncomment that (delete the #), change “tests-passed” to “stable” and rebuild.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [19. Juni 2019 um 20:52 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/3 "2019-06-19T20:52:48Z")
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.
---
### Author:  [@Json\_Blob](https://meta.discourse.org/u/Json_Blob)
#### Post date: [19. Juni 2019 um 21:07 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/4 "2019-06-19T21:07:14Z")
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.
---
### Author:  [@marianord](https://meta.discourse.org/u/marianord)
#### Post date: [19. Juni 2019 um 21:38 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/5 "2019-06-19T21:38:40Z")
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`).
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [19. Juni 2019 um 21:44 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/6 "2019-06-19T21:44:19Z")
> [@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.
> [@Updates always come before release notes](https://meta.discourse.org/t/updates-always-come-before-release-notes/88919/7):
>
> 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 …
---
### Author:  [@Json\_Blob](https://meta.discourse.org/u/Json_Blob)
#### Post date: [19. Juni 2019 um 21:48 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/7 "2019-06-19T21:48:14Z")
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
---
### Author:  [@marianord](https://meta.discourse.org/u/marianord)
#### Post date: [19. Juni 2019 um 21:49 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/8 "2019-06-19T21:49:49Z")
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`
---
### Author:  [@Json\_Blob](https://meta.discourse.org/u/Json_Blob)
#### Post date: [19. Juni 2019 um 21:54 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/9 "2019-06-19T21:54:14Z")
OH ok i was unclear then, I thought since my build had “beta” in the version I was on the beta branch. Got you.
---
### Author:  [@RGJ](https://meta.discourse.org/u/RGJ)
#### Post date: [19. Juni 2019 um 22:03 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/10 "2019-06-19T22:03:42Z")
> [@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.
---
### Author:  [@marianord](https://meta.discourse.org/u/marianord)
#### Post date: [19. Juni 2019 um 22:19 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/11 "2019-06-19T22:19:28Z")
Even if there’s a new security update between versions? As it happened between 2.2 and 2.3?
---
### Author:  [@jomaxro](https://meta.discourse.org/u/jomaxro)
#### Post date: [19. Juni 2019 um 22:23 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/12 "2019-06-19T22:23:02Z")
Correct. Any major security fix (those labeled `SECURITY:` on GitHub) are backported to both beta and stable. On occasion, though very rarely, we’ll also backport a non-security fix if we deem it critical enough.
---
### Author:  [@lucasbasquerotto](https://meta.discourse.org/u/lucasbasquerotto)
#### Post date: [20. Juni 2019 um 00:47 UTC](https://meta.discourse.org/t/upgrade-2-2-beta-to-2-3-release-not-2-4-beta/120838/13 "2019-06-20T00:47:11Z")
Just keep in mind that in some cases the stable branch might stop working with the `discourse-docker` repository.
> [@Help .. rebuild app failed](https://meta.discourse.org/t/help-rebuild-app-failed/84538/15):
>
> Ahh you’re on the stable branch…we might be missing a backport or smth.
> [@Mini\_racer causing rebuild fail](https://meta.discourse.org/t/mini-racer-causing-rebuild-fail/52231/9):
>
> Same issue for me as well. I was on stable, and couldn’t upgrade from 1.6.4 to 1.6.5 because of this issue. Now my forum is down. [https://meta.discourse.org/t/cannot-upgrade-1-6-4-1-6-5/52407?u=zsero](https://meta.discourse.org/t/cannot-upgrade-1-6-4-1-6-5/52407)
The good news is that from what I see in these cases, the discourse team backports the changes to the stable branch for it to work again.
I think that creating **tags and branches in the `discourse-docker` repository** would help a lot to avoid these kind of problems. This is up to the discourse team, tough (or you can fork the repo).