Vetting process for propose-downstream
#2208
Labels
area/rhel-ecosystem
RHEL & CentOS stream
complexity/single-task
Regular task, should be done within days.
gain/high
This brings a lot of value to (not strictly a lot of) users.
impact/low
This issue impacts only a few users.
kind/feature
New feature or a request for enhancement.
Description
During the discussion with @bookwar about CentOS Stream integration there was a point raised about being able to “vet” upstream pushing the releases to the downstream (in case the maintainers of upstream and downstream are not overlapping).
TODO:
propose-downstream
if necessaryBenefit
Reduces load on the QA and maintainers in case of any abuse happening.
Importance
We have not encountered any spamming issues yet.
What is the impacted category (job)?
Fedora release automation, Other
Workaround
Participation
The text was updated successfully, but these errors were encountered: