Skip to content

Charter

Goals

The Proposed Updates SIG fast-tracks package updates that are beneficial for those who run CentOS Stream in production, and that 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, to foster upstream collaboration.

Status

The SIG was proposed as the Fast Track SIG on the centos-devel mailing list on February 12, 2025, and approved by the CentOS Board at its March 2025 meeting as the Proposed Updates SIG (board ticket). It is currently active.

What's in scope

Fixes for packages in CentOS Stream (security fixes, bug fixes and small enhancements) that have been submitted as merge requests to the CentOS Stream package and are expected to be merged there.

Inclusion is best effort, as with everything done by volunteers: SIG members prioritize the packages they care about. If you would like a package fixed and nobody has the bandwidth for it, you are welcome to join and work on it.

What's not in scope

  • changes that are not on their way into CentOS Stream: those belong upstream, in Fedora and EPEL, or in a SIG such as Hyperscale
  • long-lived forks of Stream packages: the SIG's packages are meant to expire once Stream catches up (see Update lifecycle)

Mechanism

  • Packages are built against the same repositories as CentOS Stream itself (BaseOS, AppStream, CRB and the Stream buildroot). EPEL is not enabled.
  • The SIG ships a single repository instead of separate BaseOS, AppStream and CRB ones.
  • Builds carry a ~proposed dist tag prefix (e.g. 1.2.3-4~proposed.el10), which sorts lower than the stock Stream build of the same version-release. The change can therefore be submitted to Stream as-is, and the stock package replaces the SIG's build once it is released.
  • The vendor matches the CentOS Stream packages, so the SIG's packages interoperate with other SIGs and with systems that lock packages to their vendor.
  • Packages are built from one-off branches (e.g. the branch a merge request is sourced from), so each update starts from the current state of the published Stream package.

Resources

Communication

See the Communication channels page.

Membership

See the Membership page.