It took me until now to realize that there was a stable channel and that I need to edit the config to upgrade to it. I see an upgrade option to 3.0.0.beta16 now for my sites. If I set to the stable release now and upgrade will it go to 3.0.0.beta16 and then eventually 3.0.0 stable?

Can you explain why you believe you need to swap to stable?

I’m not sure why one would ever need a reason to run stable software. I just want less updates and stable software.

[이미지] Justin: If I set to the stable release now and upgrade will it go to 3.0.0.beta16 and then eventually 3.0.0 stable? I don’t think so. If you change to stable, you’ll only update to major releases, and 3.0.0 hasn’t been released yet. The last stable release was 2.8.0 (you can see latest …

Thanks for the info! I know he wasn’t trying to be funny, it’s just wasn’t looking to discuss reasoning, just info on when to upgrade to move to stable. I’ll keep updating while it says and switch as soon as I see 3.0.0 hit stable.

[이미지] Justin: and switch as soon as I see 3.0.0 hit stable. Be aware that the release of the major release, AFAIK, on a tests-passed branch is accompanied by the release of n+1.beta1, so if you want to avoid the word “beta” in your version, you should switch to it just before updating to n+1.…

So for instance I’m on 2.9.0.beta14 now. I should switch the branch in my config to stable and then just wait for 3.0.0 to show in my /admin section and it will only show updates to stable releases from that point on? When I change the config file do I have to restart the docker container?

You can change the app.yml now. You’ll need to wait until the release to run another command line upgrade. It’s not clear how many more beta releases there will be before a new stable is released. Stable means fewer updates, but not necessarily fewer bugs. It requires a bit more expertise to run st…

A good explanation of stable vs test-passed: [이미지] Is Discourse always in "beta"? Support There’s a good explanation of the branches we use here: So Discourse is in a perpetual beta state, meaning that we’re always working on new features and refinement…

I must admit I do feel pressured and confused by the update notification in the admin page. It is rather abrupt about telling me I should update immediately, but it tells me to update to beta software. It’s rather contradictory. I feel it should let the user know there’s an update, but only be push…

[이미지] Justin: but only be pushing the user to update ASAP if there’s a security issue or critical bug in their current build. That is exactly what is going on, when a new beta comes out, there is (almost always) a serious security issue that triggers the new version. [이미지] Justin: Altern…

지금 안정 버전으로 업그레이드하기에 가장 좋은 시기는 아닌가요?

지원

Canapin (Coin-coin le Canapin) 1월 9, 2023, 7:40오후 9

A good explanation of stable vs test-passed:

글		댓글	조회수
Stable Release Channel Support	6	2396	6월 17, 2020
When should I switch from beta release to stable release? Support	6	2691	8월 27, 2018
Switch from beta to stable releases Support	4	3073	9월 5, 2019
Secure way to configure upgrading to only stable version of forum releases? Self-hosting stable	10	1549	2월 6, 2024
Upgrade to stable versions only Self-hosting	2	965	2월 13, 2023

지금 안정 버전으로 업그레이드하기에 가장 좋은 시기는 아닌가요?

Related topics