Re: PDC replacement proposal

Current uses of PDC: 1. Critical Path Package Tracking: Bodhi leverages PDC to track packages on the critical path. /rest_api/v1/component-branches/: Specifically, Bodhi will handle the critical-path flag. Bodhi's existing framework aligns well with releases and components. To enhance this, we will create an auxiliary table that pairs this data with additional metadata, predominantly focusing on the critical-path flag. Previously, we had to query this information from PDC. It's essential to note that PDC is not the definitive source of truth for critical-path packages. The Fedora Project Critical Path Package Wiki indicates that the source of truth lies within the Fedora Comps repository. You can find specific information by searching for groups with the "critical-path-*" prefix, as demonstrated here. While the data is accessible through DNF, generating it can be time-consuming. PDC serves as a pre-computed cache. Previously, we followed this process to update it, but now we have transitioned to using this method. The primary application of this information during the Fedora release cycle is in Bodhi, where it is used to enforce stricter requirements on critical-path package updates. For further details, please refer to this link.