Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] Added release version convention for older format #24881

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

[docs] Added release version convention for older format #24881

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
459825c
added release convention for older format
aishwarya24 Nov 12, 2024
6c78137
modified stable note
aishwarya24 Nov 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/content/preview/releases/versioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,6 +43,10 @@ On rare occasions, YugabyteDB may issue a hot fix release. Hot fix releases are

{{< /note >}}

### Stable release convention prior to v2024.1

For releases prior to v2024.1, YugabyteDB used the `MAJOR.EVEN` numbering scheme (instead of `YYYY.N`) to denote stable releases. Apart from the numbering scheme, release policies, including for maintenance and patch releases, are otherwise identical. A stable release series is based on the preceding preview release series. For example, the v2.16 STS release series is based on the v2.15 preview release series.

## Preview releases

Features in preview releases are considered to be {{<tags/feature/tp>}} unless marked otherwise.
Expand All @@ -69,6 +73,17 @@ Preview releases use the numbering format `MAJOR.MINOR.PATCH.HOTFIX`, where non-

{{< /note >}}

### Preview release convention prior to v2024.1

For releases prior to v2024.1, release versions follow the versioning format of `MAJOR.MINOR.PATCH.REVISION`, where non-negative integers are used for:

- `MAJOR` — Includes substantial changes.
- `MINOR` — Incremented when new features and changes are introduced.
- `EVEN` — Stable minor release, intended for production deployments.
- `ODD` — Preview minor release, intended for development and testing.
- `PATCH` — Patches in a stable release (`MAJOR.EVEN.PATCH`) include bug fixes and revisions that do not break backward compatibility. For patches in the preview release series (`MAJOR.ODD.PATCH`), new features and changes are introduced that might break backward compatibility.
- `REVISION` - Occasionally, a revision is required to address an issue without delay. Most releases are a `.0` revision level.

## Feature maturity

YugabyteDB features are made available as one of the following:
Expand Down