Comment to 'Modzzz Update?'
Comment to Modzzz Update?

  • You should know that there is a difference between stable update channels and/or other channels. You can't expect a UNA Core update to be stable when it is delivered through a test channel, especially when it comes to third-party modules.

    Software versions are typically written in a format that includes major, minor, and patch numbers, followed by a tag indicating the development stage. Here's how the versions can be written, with examples:

    Alpha (ALPHA)

    The version is often tagged with -alpha to indicate that it's in the alpha stage.

    • Example: 1.0.0-alpha

    Beta (BETA)

    For beta versions, the tag is usually -beta or -betaX (where X is the beta iteration).

    • Example: 1.0.0-beta or 1.0.0-b1

    Release Candidate (RC)

    The release candidate is tagged with -rc and the number of the release candidate, for example, -rc1.

    • Example: 1.0.0-rc1

    Stable (or Final) (STABLE)

    The stable version is the final release and typically doesn't have a tag, though sometimes -stable is used.

    • Example: 1.0.0 or 1.0.0-stable

    Maintenance (or Patch) (MAINTENANCE)

    The maintenance or patch versions are typically written as -patchX or just X at the end of the version number.

    • Example: 1.0.1 or 1.0.0-patch1

    Long-Term Support (LTS)

    LTS versions are often tagged with -lts to indicate they will receive extended support.

    • Example: 1.0.0-lts

    General Version Format:

    Examples:

    • 1.2.3-alpha
    • 1.2.3-beta2
    • 1.2.3-rc1
    • 1.2.3
    • 1.2.3-patch1
    • 1.2.3-lts

    This format makes it easy to identify the stage of development and the version's progress over time. While many follow the Semantic Versioning (SemVer) standard (major.minor.patch-stage), others may use different formats, such as:

    • Date-Based Versions: Example: 2025.03.29 (year.month.day)
    • Incremental Build Numbers: Example: 1.2.3456 (where 3456 represents a build number)
    • Custom Naming: Example: Windows 11 22H2 or Ubuntu 24.04 LTS
    • Internal Codes: Example: v1.0-internal-2345 (for internal builds)

    Some companies may also skip version numbers (e.g., Microsoft skipped Windows 9) or use codenames (e.g., macOS "Monterey").

    So, while the general concept of alpha, beta, RC, and stable applies universally, the exact notation and tagging can vary significantly depending on the company’s internal policies.