Skip to content

Commit c0d9c89

Browse files
committed
give more clarification on the versioning differences between psp and pg 16-13
1 parent a877bff commit c0d9c89

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

docs/versioning.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,5 @@
11
# Percona Server for PostgreSQL: Version Numbering
22

3-
!!! important
4-
The below versioning is only applicable to PSP's 17.x.x releases. Only the first 2 digits scheme is used for PPG versions 13 to 16.
5-
63
Our version strings use the following format:
74

85
`MAJOR.MINOR.PATCH`
@@ -20,7 +17,9 @@ Where:
2017
| **Upstream patch/feature** | 17.1.1 | Upstream release → MINOR bump to 1, PATCH reset to 1 |
2118
| **Next Percona build** | 17.1.2 | Build #2 on upstream 17.1 |
2219

23-
!!! note
24-
The **third digit** is **always** Percona’s build number, never an upstream patch. If you see it go from …1 → …2 this means a Percona-specific update was shipped.
20+
The above versioning is only applicable to PSP 17.x.x as it is the only Percona forked server. The **third digit** is **always** PSP’s build number, never an upstream patch. If you see it go from …1 → …2 this means a PSP-specific update was shipped.
2521

22+
Since PPG 13 to 16 are pure community versions, only the first 2 digits scheme is used.
23+
24+
!!! note
2625
If you're looking for more information, check the [FAQ](faq.md#does-minor-cover-both-upstream-feature-and-patch-releases).

0 commit comments

Comments
 (0)