https://en.opensuse.org/openSUSE:Slowroll = a derivative codestream of openSUSE:Factory that uses automated rules to limit the rate of change to the codebase

Release manager: bmwiedemann

https://www.zq1.de/~bernhard/linux/opensuse/slowroll/slowroll-vs-tumbleweed-updates.svg

Slowroll update/overlay for uneven months (Jan, Mar, ...)

Slowroll update/overlay for even months (Feb, Apr, ...)

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod)

Before a version bump, I collect i586 and bootstrap binaries here. These are missing in released Tumbleweed snapshots, but are needed for building packages. Also binaries required for DVD builds, because product-builder cannot use those from download-on-demand (dod)

This provides an easy-to-use redirect for both sources and binaries in openSUSE:Slowroll:Base:N, switching every cycle (every month)

for building packages that are later released into openSUSE:Slowroll as updates

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing

https://en.opensuse.org/openSUSE:Slowroll area for building and openQA testing

This is hard with product-builder, because it does not work with dod. As a workaround we use the obsrsync script to copy binaries from Factory into :Base:1 or :2.

Packages that are specific to Slowroll and not auto-updated with the normal daily scripts.

slowrollbot will send individual packages here
and after that trigger a release of the whole project
so that only one repo-publish event happens on the main openSUSE:Slowroll update repo.