On Sat, 2020-12-05 at 10:23 -0800, Kevin Fenzi wrote: > On Fri, Dec 04, 2020 at 03:43:04PM -0600, Dennis Gilmore wrote: > > Hi all, > > > > I filed https://pagure.io/fesco/issue/2512 asking FESCo to move all > > automated emails to a separate list where people who want to follow > > can, while I was part of the proliferation of compose reports coming > > here, there is now a great deal of them, and they no longer seem to > > trigger any conversation. I think that devel list would benefit from > > having all automated reports sent to a reports-list and letting people > > bring reports over when there is something to discuss. I was asked to > > bring the request to the list for people to weigh in. > > I'm a bit torn by this. The rawhide report has actually triggered > conversation (less than 3 weeks ago) and I find it usefull to point out > things. > > Perhaps we could keep the traditional rawhide report, but send the > qa/compose test reports to another list? I quite like the Rawhide compose and compose check reports going together, because it's sort of logical: here's what changed, and here's what it broke/fixed. What about keeping those two on devel@ but I could fiddle with check- compose again and have it send the IoT and Cloud reports to iot and cloud lists (if they want them) or not send them (if they don't)? I've actually twice before written mechanisms for sending the reports for different things to different places, but they keep breaking because we keep changing what things we build, what we call them, and how we build them :/ -- Adam Williamson Fedora QA IRC: adamw | Twitter: adamw_ha https://www.happyassassin.net _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-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/devel@xxxxxxxxxxxxxxxxxxxxxxx
