I guess I’m trying to work out what you would use the tags for? If discourse_docker always works with the latest stable, you can always use the master branch of discourse_docker… 
That topic doesn’t cite a specific fix or commit, if it has been resolved it would be good to see something to the affirtmative in that sense. More than happy to nuke the sed fix if so.
Sure, I added the github link to @Falco’s post in the other topic. Here is is: FIX: We need a newer mini_racer for ruby 2.6.3 · discourse/discourse@99dd426 · GitHub
Well, there is a reason we:
- don’t default anyone to stable
- don’t recommend anyone to run stable
We run thousands of instances of Discourse. And since we deploy from tests-passed we have lots of testing on that.
When you actively go away from the standard we suggest, it’s going to be less tested. Even then we issued a whole new release to fix the issue in the same day we got a good report.
I would personally agree with the idea of tagging discourse_docker with the same version as the stable release. We currently use Puppet to automate the process of bootstrapping new Docker containers, which we pin to a specific stable release of Docker (we’re in the kind of corporate environment where the idea of running “beta” software is basically a no-go). It’d be nice if I could use that same version number as a tag in the discourse_docker repo and know that the version of the launcher I’m using is going to be able to build the version of Discourse I want to build.
Just a note that the people who maintain the software claim that the beta branch is more reliable than stable.
Quite, we live in an age where governments practice agile principles and rapidly release software under beta to their citizens.
Here’s an idea, let’s drop the ‘b’ from stable 
I always felt farming or gardening was the best metaphor for actual software development because it is a living thing. You’re growing things and that takes regular upkeep. Get busy growin’ or get busy dyin’
So stable stale is the equivalent of a fallow field?
I get it now, but your “beta” releases being more stable than non-beta is really a confusing mixed message for the rest of the world. I get it, you are developing an in-house product, which you have interest to keep growing and up to date at all times, and you are giving it away for free to everyone, but then it seems there are two choices:
- Use
tests-passedand keep updating it every couple of days, and help you fix all the the bugs and issues - Let you host it for us
Surely both scenarios are win-win for Discourse as a company. I can’t blame you for that 
But really, you should then just remove all non-beta tags, unless you want it to be “open source with a catch”.
Running Tests-passed and upgrading when there is a beta or a specific problem is what most people do. That’s a couple of three times a year.
If you’re in a corporate environment with uptime/stability expectations, then you should run a staging server.
Next time I’ll try to do just that (will use test-passed). It’s much more clear now after you explained it.
Yeah, I’m with Tomas.
This has been discussed before, but I still support the unpopular opinion of running stable for stability.
Our site has been on the stable branch for about 3 years and 603.000 posts later the experience is mostly (95%) good. The roling branches were way too volatile with UI changes, breakage and other surprises. We are especially careful about introducing change to the UX.
Sure, after every major upgrade we often need to update our slightly customized themes, adapt to other changes and usually also report some bugs.
2.3.10（stable）へのアップグレード後に問題が発生したため、このトピックにたまたま辿り着きました。
当社のサイトで使用している一部のプラグインが、Discourse のより新しいバージョンとの互換性を持つようにアップグレードされました（例：discourse-assign）。このアップグレードがネガティブな影響を及ぼしたようです。
プラグインのインストール設定を、プラグインの stable ブランチを参照するように変更しました。残念ながら、すべてのプラグインに stable ブランチが存在するわけではありません。これは Discourse エコシステム内のさらなる不整合です。
この変更が Discourse インストールに対して実際にポジティブな影響を与えるかどうかさえわかりません。
はい、Discourse 自体およびすべてのプラグイン内で stable ブランチを定義することは、安定性を高めるのに役立つでしょう。ただし、その前に「安定性」の明確な定義が必要です 
以下のアプローチは選択肢になりえません：
「ソフトウェアを維持している人々は、beta ブランチの方が stable よりも信頼性が高いと主張しています。」
どのプラグインで問題が発生していますか？
少なくとも discourse-assign です。
以下のプラグインインストールを安定版ブランチを使用するように変更し、欠落している SVG アイコンの問題を解決できる可能性があります:
- git clone --branch stable GitHub - discourse/discourse-assign: Plugin for assigning users to a topic · GitHub
- git clone --branch stable GitHub - discourse/discourse-solved: Allow accepted answers on topics · GitHub
- git clone --branch stable GitHub - discourse/discourse-canned-replies: Adds a means to insert templates from the composer. · GitHub
こちらについて、ちょっとしたアップデートです。公式プラグインとテーマコンポーネントには、互換性ファイルが用意されたと思います。例：