On 07/19/2017 09:10 AM, Peter Robinson wrote: > On Wed, Jul 19, 2017 at 2:02 PM, Dusty Mabe <dusty@xxxxxxxxxxxxx> wrote: >> >> I agree maybe I could have done more, but I maintain that I didn't do anything >> incorrect. It would be great if we actually notified when there are issues with >> rawhide (or any compose really) so many different people don't have to investigate it. > > You mean like the rawhide report? It listed the problems: > https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/thread/HCBMXIRWTSHZ5NQOU5NK4R5RFPG25VAW/ I guess. Though it doesn't seem like much discussion happens there. > >> Example. Oh crap compose X didn't build last night. I wonder what the problem is. Go >> to canonical location where discussion about compose X should happen and see if anyone >> added any notes there. Yes, I see dep issues around new version of xen and it's being >> worked on - great. Don't have to ask anyone or email anywhere. >> >> In Bodhi there is one place to go to look at discussion for a particular rpm (update) >> and if it is working or not. It would be great if we had something like this for pungi. > > Yea, and rawhide doesn't have bodhi so reading the rawhide daily > report is a good spot to see what you'd expect to be broken that day > and a list of what changed and hence what might have caused the issue. > It's probably in your inbox most mornings by the time you sit down.... > if it's not there's probably a problem.... I'm fine with that being the place where we have a discussion if it's what we want. We do have to change culture and get people to have the discussion there, though. When something is broken and being worked on let's talk about it, link to bugs, etc. Is this the wrong approach? _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
