Moin
30 ديسمبر 2024، 11:55ص
3
جميع إصدارات tests-passed لها اللاحقة -dev في النهاية نظرًا لأنه تم إضافتها للسماح بتمييز أسهل بين إصدارات “بيتا” وفرع test-passed. لذلك، لا تعني اللاحقة أن شيئًا قد تغير فيما يتعلق بما إذا كان البرنامج جاهزًا للاستخدام في بيئة الإنتاج. إنها تعني فقط “هذا إصدار واحد أثناء تطوير betaX”.
هذا هو الدليل حول كيفية تغيير الفرع الذي تتواجد عليه:
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…
وبعض المعلومات الإضافية حول الخيارات المختلفة:
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…
والموضوع حول اللاحقة -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 إعجابات