Howdy,
I'd like to propose a new Special Interest Group focused on providing primarily fixes in packages that are likely to be eventually merged into CentOS Stream directly.
# Proposer(s) - Jonathan Wright - Michel Lind (copied)
# Purpose This SIG is intended for fast tracking package updates that are beneficial for those who run CentOS Stream in production, and have a high likelihood of eventually being available in CentOS Stream (think within one minor release of RHEL, not the next major release of Stream). The SIG especially welcomes contributions from the rebuilder community aiming to foster upstream collaboration.
# Mechanism
- builds with the same repos as normal CentOS Stream packages. EPEL is /not/ enabled, but CentOS Stream buildroot will be enabled.
- but we don't distinguish between base, appstream, crb - we maintain one repo and we assume CRB is enabled (use same mechanism as epel-release to suggest people enable it)
- DistTag sorts lower than the normal Stream packages (e.g. ~el10), that way we can submit our changes as-is as a merge request
- Vendor matches CentOS Stream base packages, that way we can interoperate with packages from other SIGs, or on systems that have vendor locking enabled
- packages built from one-off branches (e.g. the branch a merge request is sourced from), so we can always start from the existing state of the published Stream package
On Wed, Feb 12, 2025 at 12:07 PM Jonathan Wright via devel devel@lists.centos.org wrote:
Howdy,
I'd like to propose a new Special Interest Group focused on providing primarily fixes in packages that are likely to be eventually merged into CentOS Stream directly.
# Proposer(s)
- Jonathan Wright
- Michel Lind (copied)
# Purpose This SIG is intended for fast tracking package updates that are beneficial for those who run CentOS Stream in production, and have a high likelihood of eventually being available in CentOS Stream (think within one minor release of RHEL, not the next major release of Stream). The SIG especially welcomes contributions from the rebuilder community aiming to foster upstream collaboration.
# Mechanism
builds with the same repos as normal CentOS Stream packages. EPEL is /not/ enabled, but CentOS Stream buildroot will be enabled.
but we don't distinguish between base, appstream, crb - we maintain one repo and we assume CRB is enabled (use same mechanism as epel-release to suggest people enable it)
DistTag sorts lower than the normal Stream packages (e.g. ~el10), that way we can submit our changes as-is as a merge request
Vendor matches CentOS Stream base packages, that way we can interoperate with packages from other SIGs, or on systems that have vendor locking enabled
packages built from one-off branches (e.g. the branch a merge request is sourced from), so we can always start from the existing state of the published Stream package
Wow, this is awesome. I do a fair bit of this kind of work, and sometimes it's annoying having to wait for it to get released...
My most recent one is with geoclue2, but I've done others in the past as well. I'm sure we can pull this content in for Hyperscale buildroots too, so work can be de-duplicated and rationalized for the wider community.
I'm happy to join up if this SIG is approved.
On 2025-02-12 09:06, Jonathan Wright via devel wrote:
Howdy,
I'd like to propose a new Special Interest Group focused on providing primarily fixes in packages that are likely to be eventually merged into CentOS Stream directly.
Thank you for proposing this, I would be happy to act as the Board sponsor for the SIG, and would definitely be interested in contributing myself as well.
Cheers Davide