Release

All builds that successfully pass all the tests and gating, and land in the c10s-pending-signed tag, get released. This happens in multiple steps.

We'll be using two terms here: composes and release.

1. Composes - the raw output of the release pipeline, containing repositories and images. These appear the moment they're created, and are not tested. See all CentOS Stream composes.
2. Release - tested content pushed to the mirrors, image registries, and other places. This is where the "Download" button goes to. See CentOS Stream mirror, the CentOS Download page, and CentOS Stream container images.

Unshipped packages

CentOS Stream only ships a subset of all available packages that can be build from its sources, reflecting the set of packages that are supported in Red Hat Enterprise Linux (RHEL). Some subpackages are only shipped in the CRB repository (e.g. most -devel packages), while others are excised altogether. It's worth noting that these unshipped packages are still built (and their artifacts can normally be found in the CentOS Stream build system). The set of packages that ends up being included in the distribution is configured in Pungi.

Requesting a package to be shipped

To request an unshipped package for inclusion, please file an issue in Jira under the RHEL project; set the component to the source package name, and the version to the corresponding CentOS Stream version (e.g. CentOS Stream 9). Explain in the issue description why you would like the package to be shipped; if the missing package is blocking an EPEL package, please state so and link to the corresponding issue on the EPEL side (e.g. a package review request). As a stopgap, you might also want to create a temporary -epel package to provide the missing subpackages (see the EPEL docs for details).