<div dir="auto"><div class="gmail_quote" dir="auto"><div dir="ltr">On Fri, 26 Oct 2018, 08:12 via llvm-dev <<a href="mailto:llvm-dev@lists.llvm.org">llvm-dev@lists.llvm.org</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word;line-break:after-white-space">
<div class="m_-7492071945443900158WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">As an llvm-bugs subscriber, I would prefer *not* to have email for every comment to every bug. That's what the CC list is for.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">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.</span></p></div></div></blockquote></div><div dir="auto">I don't agree. That is the status quo and it doesn't work. Sending email to only one person when a bug is updated is really not much better than sending email to no-one. It's unreasonable to expect a single person to triage all bugs in a component or product.</div><div dir="auto"><br></div><div dir="auto">Auto-cc also makes it impractical to track particular bugs one is actually especially interested in. It's just not a good solution.</div><div dir="auto"><br></div><div dir="auto">Having one bugs list per product, that receives email for all bug updates in that product, would seem like a decent solution. That way the various maintainers for that product can all subscribe and use their normal mail filters to classify the mail.</div><div dir="auto"><br></div><div dir="auto">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.</div><div class="gmail_quote" dir="auto"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word;line-break:after-white-space"><div class="m_-7492071945443900158WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Also +1 for UNCONFIRMED.<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">--paulr<u></u><u></u></span></p>
<p class="MsoNormal"><a name="m_-7492071945443900158__MailEndCompose" rel="noreferrer"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u> <u></u></span></a></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt">
<div>
<div style="border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Kristof Beyls [mailto:<a href="mailto:Kristof.Beyls@arm.com" target="_blank" rel="noreferrer">Kristof.Beyls@arm.com</a>]
<br>
<b>Sent:</b> Friday, October 26, 2018 10:26 AM<br>
<b>To:</b> Richard Smith<br>
<b>Cc:</b> <a href="mailto:dean.berris@gmail.com" target="_blank" rel="noreferrer">dean.berris@gmail.com</a>; llvm-dev; LLDB Dev; Clang Dev; Tanya Lattner; nd; Robinson, Paul<br>
<b>Subject:</b> Re: [cfe-dev] [RFC] LLVM bug lifecycle BoF - triaging<u></u><u></u></span></p>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<p class="MsoNormal">On 26 Oct 2018, at 04:26, Richard Smith <<a href="mailto:richard@metafoo.co.uk" target="_blank" rel="noreferrer">richard@metafoo.co.uk</a>> wrote:<u></u><u></u></p>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<div>
<div>
<div>
<div>
<p class="MsoNormal">On Thu, 25 Oct 2018 at 05:10, Kristof Beyls via cfe-dev <<a href="mailto:cfe-dev@lists.llvm.org" target="_blank" rel="noreferrer">cfe-dev@lists.llvm.org</a>> wrote:<u></u><u></u></p>
</div>
<blockquote style="border:none;border-left:solid #cccccc 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">On 5 Oct 2018, at 07:04, Dean Michael Berris <<a href="mailto:dean.berris@gmail.com" target="_blank" rel="noreferrer">dean.berris@gmail.com</a>> wrote:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><br>
<span style="font-size:8.5pt;font-family:"Menlo-Regular","serif"">Thank you for starting this conversation! I look forward to the results of the BoF discussion summarised as well.</span><u></u><u></u></p>
</div>
</blockquote>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Dean, all,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">There was a lively discussion at the BoF; we’ve tried to take notes at <a href="https://etherpad.net/p/LLVMBugLifeCycleBoF" target="_blank" rel="noreferrer">https://etherpad.net/p/LLVMBugLifeCycleBoF</a> but probably have failed to capture all the points.
The slides used to kick start the discussion can be found at <a href="https://docs.google.com/presentation/d/1ERB9IQAjSwaNpEnlbchQzd_V9IQlLOojgo9J0_NXvYA/edit" target="_blank" rel="noreferrer">https://docs.google.com/presentation/d/1ERB9IQAjSwaNpEnlbchQzd_V9IQlLOojgo9J0_NXvYA/edit</a><u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Both at the BoF and in the mail thread, there have been many suggestions for improvements. So many that if we’d want to introduce all of them at once, we’d probably get stuck and not introduce any. To try and make progress on the ones I
myself feel are most useful, I’ve volunteered for 2 actions:<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">1. Write up a proposal for documentation on what to do during bug triaging/closing/etc. I’ve just done so and put it up for review at <a href="https://reviews.llvm.org/D53691" target="_blank" rel="noreferrer">https://reviews.llvm.org/D53691</a>.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">2. Write an email to the mailing lists to ask for volunteers for being on the “default-cc” list for components, implying you’re willing to triage bugs reported against those components. I’ve decided to first try and get consensus on what
is expected when triaging a bug (see point above) before actively searching for volunteers for all components. That being said, both at the dev meeting and in the days after, I already received many requests from people to be added to the default-cc list for
specific components. Of course, I’m very happy to add people volunteering to default-cc lists, so if you don’t want to wait to get added to a default-cc list, please email
<a href="mailto:bugs-admin@lists.llvm.org" target="_blank" rel="noreferrer">bugs-admin@lists.llvm.org</a> or raise it as a ticket in
<a href="http://bugs.llvm.org/" target="_blank" rel="noreferrer">bugs.llvm.org</a> under “Bugzilla Admin”/“Products”.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">Furthermore, since the BoF, I’ve seen a quite a few requests to clean up and introduce new components in Bugzilla. We’ve implemented the changes quickly and will aim to continue to have a quick response time in the future. Please file a
ticket in <a href="http://bugs.llvm.org/" target="_blank" rel="noreferrer">bugs.llvm.org</a> under “Bugzilla Admin”/“Products” if you want to request a specific change.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">For most of the other points that were raised: I don’t currently plan on acting on them immediately myself and hope to first see an impact of the above actions.<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">In the original post, there was a suggestion to bring back the "UNCONFIRMED" status. I think that'd be a great idea, as it both makes it easy to search for untriaged bugs and to give feedback to a reporter that their bug is real and acknowledged.
Is that planned?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<div>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
<div>
<p class="MsoNormal">I hadn’t seen too much feedback on the idea for introducing (reintroducing?) the “UNCONFIRMED” status, so hadn’t planned on making changes to that now.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">However, I also think it’s a good idea, so I’ll investigate in more detail now if it wouldn’t be overly hard on the Bugzilla admin side to do so (e.g. I believe I’ll have to give all existing users the rights to be able to confirm bugs).
If the “UNCONFIRMED” status can be introduced relatively easily, I now plan to do so, and will adapt the proposed documentation at <a href="https://reviews.llvm.org/D53691" target="_blank" rel="noreferrer">https://reviews.llvm.org/D53691</a> accordingly.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks for pointing to this!<u></u><u></u></p>
</div>
<p class="MsoNormal"><br>
<br>
<u></u><u></u></p>
<div>
<div>
<div>
<div>
<p class="MsoNormal">Also, a big problem with bugzilla as we have it configured today is that commenting on an existing bug often sends mail to literally no-one. Can we reconfigure this so that llvmbugs gets mail for comments on bugs, not just for opening and
closing bugs?<u></u><u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal"><u></u> <u></u></p>
<div>
<p class="MsoNormal">I see you’ve created <a href="https://bugs.llvm.org/show_bug.cgi?id=39445" target="_blank" rel="noreferrer">https://bugs.llvm.org/show_bug.cgi?id=39445</a> for this in the mean time, and that a bit of discussion has started there - including whether sending an email on
all comments wouldn’t result in too much spam on the llvmbugs mailing list. I don’t have a strong opinion either way myself. I hope that making sure that there is at least someone on the default-cc list for every component will result in comments on bugs being
emailed to at least one person.<u></u><u></u></p>
</div>
</div>
</div>
</div>
_______________________________________________<br>
LLVM Developers mailing list<br>
<a href="mailto:llvm-dev@lists.llvm.org" target="_blank" rel="noreferrer">llvm-dev@lists.llvm.org</a><br>
<a href="http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev" rel="noreferrer noreferrer" target="_blank">http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev</a><br>
</blockquote></div></div>