On Mon, Jul 15, 2024 at 4:25 AM Pavel Raiskup <praiskup@xxxxxxxxxx> wrote: > > Hello maintainers. > > This is a gentle heads-up (at least a year in advance) that we plan to > address Fedora Copr storage consumption related to Fedora Rawhide > builds. Currently, Rawhide build results are kept indefinitely, but > this is going to change in the future. > > For the full story, see the blog post: > https://fedora-copr.github.io/posts/cleanup-rawhide-builds > > TL;DR: We plan to start monitoring build activity in Copr projects. > If no builds appear for a long time in these "rolling" chroots (such as > Fedora Rawhide), we'll disable such chroots, preserve the built results > for a while, and then delete them if no action is taken by the user. > > Hope this isn't going to cause too much inconvenience. Feel free to > discuss this here or under the blog post. Rather than keep them indefinitely, why don't the "Rawhide" builds just become the equivalent Branched buildroot? Instead of always keeping "Rawhide" around as a separate buildroot, why not just rename it at Branching and then create a NEW Rawhide chroot? -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
