Hi guys, just wanted to migrate from 2.3.0beta9 to stable release and got this error: What can I do here ? Caused by: PG::UndefinedColumn: ERROR: column “email_private_messages” of relation “user_options” does not exist LINE 1: UPDATE “user_options” SET “email_private_messages” = FALSE, … T…

You can’t switch to stable until stable catches up with the you. You can make the switch at the next stable release. Why do you want to switch to stable?

Hi, feeling a bit uneasy when running our productive environment in beta mode, to be frank … But maybe you guys can relief me of that uneasyness ? :slight_smile: Greetings, Julian

If you search here you’ll see that the tests passed branch is better supported than the stable branch. [画像] Stable branch compatibility with discourse_docker and plugins Well, there is a reason we: don’t default anyone to stable don’t recommend anyone to run stable

Thanks… then I´ll stay @ test-passed…

Have been running with tests-passed for over two years on one of my sites and can’t recall any showstopping bugs whatsoever. The bigger advantage is most plugins explicitly keep functional compatability with tests-passed so you get better third party support running that.

Hey, @Falco . This is the second time this has come up in as many weeks. Maybe there should be a comment in standalone.yml and web_only.yml that says something like ## Which Git revision should this container use? tests-passed is the best-supported and recommended for most installations rather than …

I’m torn about that. 99% of the users won’t ever see the file since ./discourse-setup hides all the complexity. The users going to the file, and reading a commented line, researching the alternative values of the key, and opting into a different one, while managing to ignore the various warnings i…

[画像] Falco: 99% of the users won’t ever see the file since ./discourse-setup hides all the complexity. Obviously those folks aren’t the problem. :slight_smile: [画像] Falco: The users going to the file, and reading a commented line, researching the alternative values of the key, and opting…

I’d say “tests-passed is STRONGLY recommended”, but you’re the one who can make commits. :wink:

tests-passed から stable への移行

サポートインストール

Falco (Falco) 2019 年 5 月 22 日午後 3:53 10

I’d say let’s delete those lines then:

github.com/discourse/discourse_docker

samples/standalone.yml

master


      
          ## Which Git revision should this container use? (default: tests-passed)
          #version: tests-passed

トピック		返信	表示
Stable Release Channel Support	6	2322	2020 年 6 月 17 日
Need a better way to explain what branch to be on, why, and what happens Support	15	1731	2022 年 9 月 30 日
Upgrade 2.2 beta to 2.3 release, not 2.4 beta Self-hosting hosting	12	2008	2019 年 6 月 20 日
Is Discourse always in "beta"? Support	23	5904	2023 年 5 月 9 日
Stable branch compatibility with discourse_docker and plugins Self-hosting stable	39	2645	2024 年 2 月 3 日

tests-passed から stable への移行

関連トピック