> So the PRs were for Rawhide, but the bug I'm trying to fix exists on all
> supported Fedora releases. I wasn't planning on updating F29 at this point
> but F30 does have a lot of life left.
>
> I don't like the idea of major upgrades within a release but the list of
> dependencies (as noted by the list of PRs) is fairly small and through my
> COPR I have found no *build* issues with the update.
>
> I'm open to suggestion here but I don't like leaving broken software in
> Fedora and basically having to tell the user, "It's fixed in Rawhide so
> you'll get it eventually..."
>
> Thoughts?

Let's get everything built and tested in rawhide first. Based
on how this turns out, an update in F30 and F31 might be appropriate
(with a suitably long testing period, etc). I agree that if the version
in stable Fedora is sufficiently broken, it's better to release an
working update with major version changes than to do nothing.