From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2240#note_1230246925 @prarit - hmm, ok I am torn here. I thank you for respecting the 'do not break ARK approach'. But then I wonder what is the value of this in ARK (besides the obvious don't lose changes)? Because once your fork for RHEL, you are now stuck for XX weeks until this backlog of errors are cleaned up. Or you just disable it to move forward (which probably happened for RHEL-9). The value of ARK/rawhide is discovering potential RHEL problems early and resolving them before RHEL sees them. Of course, fixing them can be a firedrill but I am trying to find techniques to minimize that and become more async. Can we say upstream GA needs to be -Werror clean (for ARK), but give ourselves ~8 weeks to resolve them. This means using CONFIG_WERROR becomes a RHEL thing but maybe we track WARNINGS during the -rc cycle that need resolving? Just trying to brainstorm using the idea of -Werror for ARK to give value to RHEL without creating the OMG firedrill behind it. _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-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/kernel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
