Moin
December 30, 2024, 11:55am
3
All versions of tests-passed have the -dev suffix at the end since that was added to allow easier differentiation between “beta” releases and the test-passed branch. So the suffix doesn’t mean anything changed in terms of whether the software is ready for use in production. It just means “this is one version during the development of betaX.”
This is the guide about how to change the branch you are on:
This guide explains how to configure a supported tracking branch for your Discourse instance to manage software updates.
Required user level: Systen Administrator
Console access is required.
Managing your Discourse instance’s tracking branch determines the frequency and type of updates you receive. This guide explains the different tracking branches available and provides a step-by-step approach to changing the branch on your setup.
Summary
Disco…
And some more information about the different options:
This guide explains the different types of Discourse releases and how different channels are used for updates.
Required user level: All users
Release channels
Discourse has four primary release channels, each serving a different purpose: main, tests-passed, beta, and stable.
The default channel used when installing a production version of Discourse is tests-passed.
The naming conventions used by Discourse differ a bit from other software companies:
main
O…
and the topic about the -dev suffix:
On tests-passed, starting with 3.2.0.beta1-dev, Discourse core version numbers will include a -dev suffix to indicate that they’re not the final ‘release’ versions of a beta. This suffix doesn’t appear in the UI, so this is a technicality which will have no impact on the vast majority of people.
For the technical details, see below:
In the beta series for Discourse 3.1 and below, our versioning strategy was to ‘release’ a beta, and then leave the version number in tests-passed exactly the sam…
7 Likes