Nicolas Mailhot via devel <devel@lists.fedoraproject.org> igorleak hau idatzi zuen (2019 mai. 6, al. 09:59):
Le dimanche 05 mai 2019 à 16:14 -0600, Chris Murphy a écrit : > > Right and that's the same with beta testing, which is how bugs like > this can sometimes not even get found until after release. A lot of > tests are done on pristine systems that are throw away. It's entirely > understandable few people want to test Fedora pre-release on their > rock solid 5+ year old Fedora system, but we actually stumbled on > this > in some sense by luck of alternate arch acting like a canary. That's not true, many boot problems are found quite early in the process by rawhide users, but rawhide users feedback is not taken into account by installer folks because they don't look at boot problems before quite late in the cycle, when rawhide users have already moved on manually, and the default solution is always to reinstall from scratch. So problems are found, just not fixed About this specific bug... We found this bug before releasing, but it is not a release blocking bug (the upgrade criteria just cover clean n and n-1 upgrading to n+1 and this bug just happens whith continously upgraded systems since fc21 or lower) so QA folks talked with bootloader ones, it was a difficult bug to fix without breaking things/overwriting other bootloaders and there was no time to announce, discuss and decide about policy changes so we went ahead documenting it on common bugs.
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
