> I'm not seeing any kernel 5.7.1, 5.7.2 kernel builds in koji and on it's > way to <=33 now after 5.7.1 had been released ( expected after 5.7.1, > there are two weeks since last 5.7.x build ) is that part of this new > workflow along with this significant CI noise and needless one line ack Nothing at all related to it what so ever. The standard process for new stable kernels in Fedora stable releases has been "sometime after the .3 release" and has been that as long as I've been involved in kernel stuff (about 10 years). The process for stable lands the new kernel into the stabilization in dist-git, and 5.7.2 has been there since Wed 10th, from there the various maintainers check it's ready and then a test week is scheduled and initial builds are done. The process is unchanged by any of the changes for the rawhide kernel building which has the new process. Justin is on PTO this week, later this week upstream will no doubt do a 5.7.3 release and I suspect next week there will be a test day. > messages on what was otherwise a mailinglist in which people could have > meaningful discussions ( as of today 41 messages of pure noise until you > reach Justin Forbes "Re: Streamlining the ARK config process" )? As one of the community kernel maintainers doing a bunch of the arm related kernel stuff in my own time I am actually just fine with the the messages, the increase in actively is larger than the very quiet kernel list before but it's still completely manageable and with headers etc the messages are very easily filtered if you don't like them. > Did not the RH management that conducted this takeover of the Fedora > kernel process even consider creating a separated mailinglist ( > kernel-ci, kernel-build whatever ) when it started projecting it's > internal spaghetti mess of process,workflows and cluttered pipelines > onto the community? Well as far as I'm aware "RH management" had nothing to do with the change of process and it came directly from the actual kernel maintainers both in Fedora and Red Hat. It will in the medium term allow the wider community have a say and more of an impact as to what RHEL kernels look like and opens up the process more, with my community maintainer hat on (and I really have zero to do with the internal RHEL kernel process) I actively welcome this. Peter _______________________________________________ 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
