You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should have automated tooling which monitors Bodhi for:
security updates,
for packages in Fedora CoreOS,
which have a larger NEVRA than the corresponding package at the head of one or more production or development branches,
which have not been fixed by a backport, and
which have not been explicitly ignored for that branch,
and notifies us. We can then
update branch lockfiles to accept the package, optionally performing an OS release,
backport the fix and update lockfiles to accept the backport, optionally performing an OS release, or
explicitly ignore the update with respect to certain branches, e.g. if it's not important enough to fix out-of-cycle.
The tool should complain periodically until we do one of those things.
We'll need a way to record that a backport includes the security content of a particular Bodhi update, and to record that we're ignoring certain security updates. I think it makes sense to create a new file for that in each fedora-coreos-config branch.
To support the next stream, the tool will need to monitor multiple Fedora releases. For maximum advance notice, we'll probably want to recognize an update from the moment it's created in Bodhi, even before it's pushed to updates-testing.
The text was updated successfully, but these errors were encountered:
We should have automated tooling which monitors Bodhi for:
and notifies us. We can then
The tool should complain periodically until we do one of those things.
We'll need a way to record that a backport includes the security content of a particular Bodhi update, and to record that we're ignoring certain security updates. I think it makes sense to create a new file for that in each fedora-coreos-config branch.
To support the
next
stream, the tool will need to monitor multiple Fedora releases. For maximum advance notice, we'll probably want to recognize an update from the moment it's created in Bodhi, even before it's pushed toupdates-testing
.The text was updated successfully, but these errors were encountered: