On Tue, May 2, 2017 at 11:34 PM, Adam Williamson adamwill@fedoraproject.org wrote:
OK. And to be honest, this isn't limited to release validation and blocker bugs. What generally happens when an RHBZ report gets kicked upstream is the bug gets fixed...upstream. Often it only gets fixed on git master, which means it will likely *never* get fixed in the Fedora release it was actually filed against. If we're lucky the fix might also be committed to the most recent stable branch, which is probably the GNOME in the most recent Fedora release, so if there's ever another point release on that branch (often there aren't any after .2), the fix might *eventually* make its way back to the most recent Fedora release. But if we're at .2, or the bug was filed on the previous stable Fedora release, the fix may well never actually make it back to the Fedora release the reporter is running without someone taking ownership and bugging people to commit to different branches, do point releases, and ship updates to Fedora.
Some maintainers are better about doing stable releases than others. Of course we can patch things downstream, but in general, if we're doing that, the patch is probably needed by other distros too. So when you run into such situations, feel free to ping me or any other release team member, and we will try to get a release. Once it is released upstream, Kalev's scripts will have a Fedora update rolling quickly thereafter.
Michael