Branches
Branches in CentOS¶
The convention on the Red Hat CentOS Stream GitLab is for packages
to have a branch per major CentOS Stream version, so you get c9s
, c10s
, etc. These branches host the sources
for CentOS and Red Hat Enterprise Linux (RHEL).
Special note about (Modular) Application Streams¶
Packages shipped as part of module streams can have additional branches, usually named <dist>-stream-<modulestream>
.
For example, the softhsm package has a c8s-stream-DL1 branch
,
signifying it is shipped as part of the DL1
module stream (of the idm
module, in this case). On a running system,
dnf module provides softhsm
would also point out the origin of this package.
Branches in Hyperscale¶
CentOS Hyperscale is maintained on the CentOS GitLab. Packages are maintained in the Hyperscale/rpms
group in GitLab.
Hyperscale branches are maintained in cXs-<hsvariant>
, where cXs
refers to the CentOS Stream version (e.g. c10s
for CentOS Stream 10),
and <hsvariant>
refers to the Hyperscale SIG tag it was built for. Below is a table explaining the relationship.
Hyperscale tag | Variant tag |
---|---|
main | hs |
spin | hs-spin |
experimental | hsx |
kernel | hsk |
asahi | hs+asahi |
gnome | hs+gnome |
hs+fb | |
intel | hs+intel |
Some older packages may follow the legacy conventional cXs-sig-hyperscale
branch model.
In the further past, we also used cXs-sig-hyperscale-experimental
branches for packages targeting the experimental repository.
These are deprecated and will be removed once all packages have been migrated to the current convention.