Skip to content

PSP 17.11 18.6 Q3 release changes - #19

Closed
surbhat1595 wants to merge 1 commit into
mainfrom
Q3PG1718
Closed

PSP 17.11 18.6 Q3 release changes#19
surbhat1595 wants to merge 1 commit into
mainfrom
Q3PG1718

Conversation

@surbhat1595

Copy link
Copy Markdown
Collaborator

No description provided.

@github-actions

github-actions Bot commented Aug 31, 2026

Copy link
Copy Markdown

OBS Build Check — ❌ Builds failed

Packages for this PR are being built at isv:percona:PR:pr-19.

Packages
Built from PR sources 32
Reused from main binaries 53
Repository ✔ Succeeded ✗ Failed ⛔ Broken ⚠ Unresolvable — Excluded
Debian_13 28 2 0 0 2
RockyLinux_9 32 0 0 0 0
Ubuntu_26.04 30 2 0 0 0
openSUSE_Tumbleweed 32 0 0 0 0
Total 122 4 0 0 2

Updated: 2026-09-01 10:05 UTC

@surbhat1595
surbhat1595 force-pushed the Q3PG1718 branch 2 times, most recently from 31ba54c to bd209fd Compare August 31, 2026 11:10
The Percona fork tagged the new releases as PSP-16.15.1 / PSP-17.11.1 /
PSP-18.6.1 instead of the release-X.Y.Z naming used up to 17.10.2 /
18.4.2, so the revision form introduced with PERCONA_PG_PATCH_VERSION
(release-%!{PG_VERSION}.%!{PERCONA_PG_PATCH_VERSION}) keeps resolving
to the release-* *branches* and would never pin itself to a tag.

Switch staging/17, staging/18 and staging/16/tde to
PSP-%!{PG_VERSION}.%!{PERCONA_PG_PATCH_VERSION}.  Each PSP tag
currently points at the exact head of the corresponding release-*
branch (PSP-16.15.1 = c0d38ac6, PSP-17.11.1 = d2798ace,
PSP-18.6.1 = 19c3033d), so the built source is unchanged; the
revision just stops being a moving ref, as a staging tier expects.

Signed-off-by: Ricardo Dias <ricardo.dias@percona.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants