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.

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

[doc] Clarification of release numbering #25361

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open
Changes from 1 commit
Commits
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
4 changes: 2 additions & 2 deletions docs/content/preview/releases/versioning.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,9 +32,9 @@ Stable release versions use the numbering format `YYYY.N.MAINTENANCE.PATCH` as f
- For YugabyteDB, backward compatible bug fixes are included.
- For YugabyteDB Anywhere, functionality may be added in a backward compatible manner.

- `PATCH` - Includes bug fixes and revisions that do not break backward compatibility.
- `PATCH` - Includes bug fixes and revisions that do not break backward compatibility. Patch releases are typically for specific point issues, and usually offered only applicable to specific customers.
ddhodge marked this conversation as resolved.
Show resolved Hide resolved

On rare occasions, YugabyteDB may issue a hot fix release. Hot fix releases are for specific point issues, and usually offered only to specific customers. Hot fix releases append an additional number to the release versioning convention as `YYYY.N.MAINTENANCE.PATCH.HOTFIX`.
(Prior to version 2024.1, stable releases used a convention similar to [preview releases](#preview-releases), except the MINOR integer is always even.)

{{< note title="Important" >}}

Expand Down