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.

[image] 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 updates in #release-notes) [image] 2.8.0: Major Release megaphoneAnnouncements Discourse 2.8.0 release! We’ve completed the 2.8.0 development cycle and pushed out the final release. Check out our blog post, as well as all the 2.8.0.betaX #release-notes topics for details. [image] Justin: I’m not sure why one would ever need a reason to run stable software I don’t think Stephen was trying to be funny. Stable is used in a meaning of a keyword for app.yml, not as an English word. Reason being, the other (default) keyword, tests-passed can be described as stable too: it’s unlikely to be broken[1], and in fact, can be more “stable” (English-wise) if you update plugins and/or theme-components more frequently than you wish to update Discourse. in my 2 years running Discourse, I’ve never had a situation when something was broken because of some fresh commit ↩︎

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.

[image] 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.beta1. [image] Justin: wasn’t looking to discuss reasoning Sometimes[1] the questions are formulated based on faulty assumptions, and it’s better to understand those early on. one could argue quite often, if we deal with “please help” topics. this is IMHO based on discussions on my forum too ↩︎

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 stable than tests passed. Critical security updates do get included in stable, but ux issues are likely to remain broken until the next stable release. Third party plugins are less likely to work with the stable branch as it’s less well tested. If you want fewer updates you can just update less frequently.

A good explanation of stable vs test-passed: [image] 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. In our case beta does not mean unstable; we host sites with millions of monthly pageviews on our tests-passed and beta versions.

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 pushing the user to update ASAP if there’s a security issue or critical bug in their current build. Perhaps the beta tag could be removed if it is considered stable or change it to tests-passed so admins can feel more comfortable updating, knowing they’re getting fully tested and stable software. Alternatively it could drop the beta tag and be called stable as that’s what I’m reading here, then the current stable release could be called LTS.

[image] 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. [image] Justin: Alternatively it could drop the beta tag and be called stable as that’s what I’m reading here, then the current stable release could be called LTS. Which would be a pretty good (better, IMO) way of looking at things indeed.

Is now the best time to upgrade to a stable release?

Product Support

Canapin (Coin-coin le Canapin) January 9, 2023, 7:40pm 9

A good explanation of stable vs test-passed:

Topic		Replies	Views
Stable Release Channel Product Support	6	2527	June 17, 2020
When should I switch from beta release to stable release? Product Support	6	2756	August 27, 2018
Switch from beta to stable releases Product Support	4	3126	September 5, 2019
Secure way to configure upgrading to only stable version of forum releases? Self-hosting stable	10	1669	February 6, 2024
Upgrade to stable versions only Self-hosting	2	1004	February 13, 2023

Is now the best time to upgrade to a stable release?

Related topics