Skip to content

Commit

Permalink
docs: incorporate bases
Browse files Browse the repository at this point in the history
  • Loading branch information
medubelko committed Nov 28, 2024
1 parent 06d5514 commit bdf786d
Showing 1 changed file with 11 additions and 5 deletions.
16 changes: 11 additions & 5 deletions docs/release-notes/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,10 @@ Canonical is committed to supporting the <"latest major release" or "last two
major releases"> of Starcraft. <Optional: "We forward-port changes in older
releases to the latest release, if they're compatible.">

Starcraft is released according to the Semantic Versioning 2.0.0 scheme with
Starcraft is released when it achieves development milestones in its product
lifecycle. It doesn't follow a predefined release cadence.

Starcraft release naming follows the Semantic Versioning 2.0.0 scheme with
numbers for major, minor, and patch versions.

.. list-table::
Expand All @@ -64,17 +67,17 @@ numbers for major, minor, and patch versions.
- Significance
* - Major
- **3**.1.2
- A change that breaks compatibility with the previous version.
- <Apps: "A change that drops support for an earlier software base.">

<Libraries: "A change that breaks compatibility with the previous
version.">
* - Minor
- 3.\ **1**\ .2
- A new feature within the major version.
* - Patch
- 3.1.\ **2**
- A bug fix within the major or minor version.

Starcraft is released when it achieves development milestones in its product
lifecycle. It doesn't follow a predefined release cadence.


Long-term support
-----------------
Expand All @@ -83,6 +86,9 @@ Starcraft doesn't have long-term support (LTS) releases. However, we typically
deliver a compatibility patch shortly after Ubuntu LTS releases to ensure
continuity.

Starcraft software bases are derived from Ubuntu LTS releases, and their
development keeps pace with the OS's new releases and support lifecycle.

.. toctree::
:maxdepth: 1

Expand Down

0 comments on commit bdf786d

Please sign in to comment.