Re: [lldb-dev] [cfe-dev] [llvm-dev] [RFC] LLVM bug lifecycle BoF - triaging

2018-10-31 Thread Zachary Turner via lldb-dev
I can tell you that in LLDB we already do get CC'ed on the list for every bug. I will grant you that the volume of bugs in LLDB is much lower than other lists, but I find it very helpful. It gives visibility to bugs that would otherwise be seen by nobody. On the other hand, I'm intentionally uns

Re: [lldb-dev] [cfe-dev] [llvm-dev] [RFC] LLVM bug lifecycle BoF - triaging

2018-10-31 Thread via lldb-dev
If the admins guarantee that there is at least one auto-cc (who promises to pay attention) for each component, I think that is sufficient. I don't agree. That is the status quo and it doesn't work. No, it's not the status quo, because we've only started soliciting auto-cc subscribers in the past

Re: [lldb-dev] [cfe-dev] [llvm-dev] [RFC] LLVM bug lifecycle BoF - triaging

2018-10-31 Thread Richard Smith via lldb-dev
On Wed, 31 Oct 2018, 10:47 David Greene via cfe-dev Richard Smith via cfe-dev writes: > > > In fact, I think it'd be entirely reasonable to subscribe cfe-dev to > > all clang bugs (fully subscribe -- email on all updates!). I don't see > > any reason whatsoever why a bug update should get *less*

Re: [lldb-dev] [cfe-dev] [llvm-dev] [RFC] LLVM bug lifecycle BoF - triaging

2018-10-31 Thread David Greene via lldb-dev
Richard Smith via cfe-dev writes: > In fact, I think it'd be entirely reasonable to subscribe cfe-dev to > all clang bugs (fully subscribe -- email on all updates!). I don't see > any reason whatsoever why a bug update should get *less* attention > than non-bug development discussion. Some of us