Skip to content

Update YaST branches for SLE16 #376

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

Merged
jreidinger merged 2 commits into from
Sep 1, 2026
Merged

Update YaST branches for SLE16 #376

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
95358c5
update list of yast branches
jreidinger Sep 1, 2026
b7076a7
Apply batched suggestions from code review
jreidinger Sep 1, 2026
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
8 changes: 6 additions & 2 deletions doc/maintenance-branches.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -160,17 +160,21 @@ Already known names for branches:
- `SLE-10-SP*`: SLE 10 Service packs
- `Code-11`: SLE 11 GA
- `Code-11-SP*`: SLE 11 Service packs
- `SLE-*-GA`: SLE 12 and later GAs
- `SLE-*-SP*`: SLE 12 and later Service packs
- `SLE-*-GA`: SLE 12 and 15 GAs
- `SLE-*-SP*`: SLE 12 and 15 Service packs
- `openSUSE-1*`: respective openSUSE release
- `openSUSE-4*`: openSUSE leap releases (see below)
- `SLE-16.*`: SLE16 and Leap16 releases matching agama naming

Maintenance branches for Leap only make sense for a few repositories.
For most YaST packages, openSUSE Leap and SLE share the same code and
maintenance updates and, thus, only the corresponding `SLE-*` maintenance
branch is used. Leap maintenance branches will be created manually in a case by
case basis, only when needed and only for repositories that affect openSUSE but
not SLE.
For SLE-16.*, the situation is different as YaST transitions into a backend-only state for Agama,
which causes branches to be created only on demand when a backport of a fix is needed.
A Leap 16 branch is not planned as product-specific settings are kept in agama-products.

Working with SLE 10 and SLE 11
------------------------------
Expand Down
Loading