proposal: package change metadata We're working on bodhi-scraper which is part of larger effort in rpm-ostree to optimize packing images. We require a metadata file (frequencyUpdateInfo.json) in the repodata of every (Fedora/RHEL/SCOS/Kionite)<Release> repository. This file will contain the list of all updates to all of the packages of the specific release. These list of updates are more comprehensive than those present in updateinfo.xml. We then combine the frequencyUpdateInfo.json of all the current and pending releases and process it to create a file.

As an enterprise software company with a FOSS development model, source code is fundamental to what Red Hat does. We are part (or the primary driver for) many different communities that manage their source code in different ways, from Github, Gitlab, old Sourceforge projects, GNU Savannah, and more. However, when we ship (compiled) code to customers, we need to be able to fix an issue in that project even if the original upstream source code repository is (temporarily or permanently) unavailable.

I'll be part of an AMA session on FCOS! Time: 9am PST/noon EST Link: https://commons.openshift.org/#event|fcos-ama-session-with-fcos-wg-and-technical-leads|1136 Here are some sample questions to get you thinking! Q: How do I test e.g. a kernel patch to see if it fixes an issue in my OKD cluster? Q: If Fedora Workstation defaults to BTRFS, would FCOS switch too?