This question is somewhat following on from the new “Weekly Summaries” (which I think are a great idea!): Weekly Discourse Summary?. These summaries are going to be about the beta releases, while the default setup for self-installers is tests-passed.
I know there’s a lot of discussion about the different branches on Meta, so I’ll try and keep this as specific as possible.
This is from 2014:
Discourse has 3 official branches:
- tests-passed: updated most frequently after our test suite runs. This is the branch we deploy most of our customers on.
- beta: updated weekly(ish), a snapshot of tests-passed.
- stable: where our major releases live (with security fixes backported as they arise)
I’m currently running on tests-passed, which obviously has the advantage of getting features as soon as they’re released. The disadvantage is that there are very often little bugs in functionality present in tests-passed. They get fixed extremely quickly, but the bug will still be present on my forum until I manually go and update again. Often I’ll only do that once someone has complained about a bug, which is too late!
I’m curious how the team deal with this on your own hosting. I know that meta/try exactly follow the latest commit to tests-passed, but what about your customers?
Do you wait until tests-passed is in a “good” state, and then deploy to customers? Or is the beta branch a good representation of what gets deployed?