<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Jan 3, 2014 at 7:08 AM, Sean Dague <span dir="ltr"><<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 01/03/2014 09:44 AM, Anne Gentle wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Fri, Jan 3, 2014 at 7:52 AM, Thierry Carrez <<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a><br></div><div class="im">
<mailto:<a href="mailto:thierry@openstack.org" target="_blank">thierry@openstack.org</a>><u></u>> wrote:<br>
<br>
Tim Bell wrote:<br>
> Is there a mechanism to tag changes as being potentially more<br>
appropriate for the more ops related profiles ? I'm thinking more<br>
when someone proposes a change they suspect could have an operations<br>
impact, they could highlight this as being one for particular focus.<br>
><br>
> How about an OpsImpact tag ?<br>
<br>
I think such a tag would help. That would encourage ops to start looking<br>
more regularly into proposed changes by highlighting the few reviews<br>
that are most likely to need their expertise.<br>
<br>
We could have that tag post reviews to the -operators ML (in the same<br>
way SecurityImpact posts to the -security ML), which would additionally<br>
reinforce the need for this list as a separate list from the openstack<br>
general list.<br>
<br>
<br>
I think this is a good idea, though I have to say when we were using<br>
DocImpact in this way, it kills conversational dialog on the mailing<br>
list because all the robots start talking on your list as more people<br>
use the flag. We have since moved to automatically logging a doc bug<br>
rather than posting to the mailing list.<br>
<br>
Still, I think it's worth trying for OpsImpact because there's not a<br>
secondary place to log the impactful patches. Nice idea, Tim!<br>
</div></blockquote>
<br>
If we are going down this path, it would be good to give reviewers a training set. So a dozen patches that someone things would be good OpsImpact and a dozen patches which clearly aren't.<br>
<br>
Otherwise I fear we're making a lot of assumptions about what people believe are and are not OpsImpact and I don't think it will be that helpful.<br>
<br>
I also really think that this is the less useful approach than taking those key ops issues into the CI toolchain. And if people only have one place to spend energy, spending it on the CI side is way more beneficial.<div class="im HOEnZb">
<br></div></blockquote><div><br></div><div>++ to both of these. My biggest concern with the OpsImpact tag idea so far is that I don't know what should get it.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb">
<br>
-Sean<br>
<br>
-- <br>
Sean Dague<br>
Samsung Research America<br>
<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a> / <a href="mailto:sean.dague@samsung.com" target="_blank">sean.dague@samsung.com</a><br>
<a href="http://dague.net" target="_blank">http://dague.net</a><br>
<br></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.<u></u>org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>