Re: Fedora Linux 35 Final blocker review summary

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, I understand the point, I too have lived with some of these bugs and don't noticed them until now. It's fair to move on and don't hold the release hostage as Matthew said, but for that I think we should add some rule, policie or something to the release blocking criteria allowing that, because most of these bugs meet one or other criteria and we must be consistent.

Geraldo

Em dom., 17 de out. de 2021 às 05:54, Mattia Verga <mattia.verga@xxxxxxxxxxxxxx> escreveu:
On 16/10/21 22:15, Geraldo Simião Kutz wrote:
So, by that thought, if a bug meet the blocking criteria but have not been caught in the previous release by a mistake of the team (as no one pointed before as blocker bug) that bug can no more be blocker? 


That's my opinion. If the bug is already present in a previous release why it should block the next? If no one had never reported or even noticed the bug in the previous version I doubt it should be considered a blocker.

In this specific case, I used to have a bare metal machine which had been updated during years between Fedora releases. I was using F34 on that old machine and I never noticed neither the plasma-discover or the KScreenLocker bugs. I then upgraded my PC, installed F34 from clean and started noticing those bugs. I can live with them during my everyday workstation usage, certainly they're annoying (especially the KScreenLocker bug, the plasma-discover bug has disappeared after some upgrades), but that wouldn't prevent me from upgrading to F35.

I must also add that, searching in the web about those bugs, I can found users hitting them long time ago. But KDE never fixed them. I also tried to upgrade KScreenLocker to the next available version (available only in F36) and only partially fix the problem. So, if we had to wait for KDE to fix those bugs, we are going to delay F35 release for a long time...

Mattia

_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Index of Archives]     [KDE Users]     [Fedora General Discussion]     [Older Fedora Users Mail]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Maintainers]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Triage]     [Coolkey]     [Yum Users]     [Yosemite Forum]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux