Moin
Dezembro 30, 2024, 11:55am
3
Todas as versões de tests-passed têm o sufixo -dev no final, pois foi adicionado para permitir uma diferenciação mais fácil entre os lançamentos “beta” e o branch test-passed. Portanto, o sufixo não significa que algo mudou em termos de se o software está pronto para uso em produção. Apenas significa “esta é uma versão durante o desenvolvimento de betaX”.
Este é o guia sobre como alterar o branch em que você está:
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…
E mais algumas informações sobre as diferentes opções:
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, latest, beta, and stable.
The default channel used when installing a production version of Discourse is latest.
The naming conventions used by Discourse differ a bit from other software companies:
main
On GitHub…
e o tópico sobre o sufixo -dev:
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 curtidas