How about this:
Drop the term 'jump scare' entirely. IMHO it just sounds bad.
Rework the change so it's basically planning on making this change in
f38.
Before f38 beta freeze, change owners/fesco looks at the state of things
and decides if it can remain on in f38 and if not, it gets reverted and
moved to f39.
In the run up to f38 beta we could:
* run a series of test days. perhaps one before you enable it in
rawhide, one a month or two later and one right before f38 beta
freeze?
* see if openqa might have some way to set TEST-FEDORA39 and re-run
tests on a compose or updates? This might be a good thing to try and do
before landing it in rawhide.
* setup a tracking bug to track the issues, so we can make a more
informed decision before f38 beta.
Thoughts?
kevin