Hi!
I saw that V2.7.0 is available.
I have 2.7.0.beta9 and want to upgrade to 2.7.0 final.
My question is: How do I do this?
סיכום מבוסס בינה מלאכותית
In a discussion titled “Upgrade from beta to final” under the Support category, user daemon asks how to upgrade from version 2.7.0.beta9 to the final 2.7.0 release. pfaffman advises waiting for an official announcement and notes that upgrading now might land them on 2.8.0.beta1, linking to the beta1 announcement. jomaxro clarifies that switching to the stable branch is possible by editing app.yml to change version: tests-passed to version: stable, but warns this is not generally recommended outside specific use cases. daemon confirms understanding and asks for clarification on switching branches; jomaxro explains that they’re technically on tests-passed, not beta, and recommends staying there unless there’s a specific need for stability. daemon concludes they’ll wait for 2.8.0.beta1, acknowledging that “beta” versions are essentially minor releases. jomaxro affirms this and thanks them. Finally, sunjam mentions their team may switch to stable temporarily to reduce update frequency for an active user, with the option to revert if needed.
Wait a tiny bit more. There will be an announcement soon, I’d think.
Also, if you want to switch to stable now is the time. I suspect that if you run an upgrade right now, you’ll end up on v2.8.0.beta1.
EDIT: See? 2.8.0.beta1: The beginning of Discourse 2.8 'Audion'
This is key. Before you update you need to switch to the stable branch. That said, we don’t recommend running stable, outside super specific use cases.
Ok, so I should stay on the beta path?
If I want, how do I switch to stable? I’ve looked in the app.yml but couldn’t find anything about stable/beta.
That is our standard recommendation, yes. Unless you have a very specific reason to move to stable (feel free to share your reasoning here) you should stick with tests-passed, the default. Note that you’re not technically on beta, but tests-passed. However, you get notified of new betas, and likely only update when that happens, which is why it may seem like you’re on the beta branch.
Look for the line that looks like this:
version: tests-passed
To switch to stable change that to:
version: stable
(be careful not to modify indentation).
Ok, so 2.7.0.beta9 is only a name and not technically an alpha/beta/rc. I understand!
So I’ll do nothing except waiting for the next “beta” release which will be 2.8.0.beta1.
Thank you all very much!
Correct. Think of betas as “minor” or “point” releases.
Of course!
I’m thinking we will switch to “Stable” for the time being since one active user has requested fewer updates & changes. If it doesn’t work I suppose we can always switch back to the standard beta release schedule.