<div dir="ltr"><div>Thanks for the clarifications about official tags. I was the one creating random/non-official tags for tripleo bugs. </div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><div>Although this may be annoying for some people, it helped me while ruckering/rovering CI to open unique bugs and avoid dups for the first time(s).<br></div></div></span></div><div><div>There isn't a standard way of filing a bug. People open bugs using different/<span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">non-standard</span> wording in summary and description.<br></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I just thought it was a good idea to tag featuresetXXX, ovb, branch, etc., so when somebody asks me if there is a bug for the job XYZ, the bug could be found more easily.</span><br></span></div><div><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></span></div><div>Since sprint 10 ruck/rover started recording notes [1] and this helps to keep track of the issues.</div><div>Perhaps the CI team could implement something on CI monitoring that links a bug to the failing job(s), e.g: <jobname> [LP XXXXXX].</div><div><br></div><div>I'm doing a cleanup for the open bugs removing the non-official tags.</div><div><br></div><div>Thanks,</div><div><br></div><div>--Folco</div><div><br></div><div>[1] <a href="https://review.rdoproject.org/etherpad/p/ruckrover-sprint11">https://review.rdoproject.org/etherpad/p/ruckrover-sprint11</a></div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Apr 6, 2018 at 6:09 AM, Jiří Stránský <span dir="ltr"><<a href="mailto:jistr@redhat.com" target="_blank">jistr@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 5.4.2018 21:04, Alex Schultz wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Thu, Apr 5, 2018 at 12:55 PM, Wesley Hayutin <<a href="mailto:whayutin@redhat.com" target="_blank">whayutin@redhat.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
FYI...<br>
<br>
This is news to me so thanks to Emilien for pointing it out [1].<br>
There are official tags for tripleo launchpad bugs. Personally, I like what<br>
I've seen recently with some extra tags as they could be helpful in finding<br>
the history of particular issues.<br>
So hypothetically would it be "wrong" to create an official tag for each<br>
featureset config number upstream. I ask because that is adding a lot of<br>
tags but also serves as a good test case for what is good/bad use of tags.<br>
<br>
</blockquote>
<br>
We list official tags over in the specs repo[0]. That being said as<br>
we investigate switching over to storyboard, we'll probably want to<br>
revisit tags as they will have to be used more to replace some of the<br>
functionality we had with launchpad (e.g. milestones). You could<br>
always add the tags without being an official tag. I'm not sure I<br>
would really want all the featuresets as tags. I'd rather see us<br>
actually figure out what component is actually failing than relying on<br>
a featureset (and the Rosetta stone for decoding featuresets to<br>
functionality[1]).<br>
</blockquote>
<br></span>
We could also use both alongside. Component-based tags better relate to the actual root cause of the bug, while featureset-based tags are useful in relation to CI.<br>
<br>
E.g. "I see fs037 failing, i wonder if anyone already reported a bug for it" -- if the reporter tagged the bug, it would be really easy to figure out the answer.<br>
<br>
This might also again bring up the question of better job names to allow easier mapping to featuresets. IMO:<br>
<br>
tripleo-ci-centos-7-containers<wbr>-multinode -- not great<br>
tripleo-ci-centos-7-featureset<wbr>010 -- not great<br>
tripleo-ci-centos-7-containers<wbr>-mn-fs010 -- *happy face*<br>
<br>
Jirka<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
Thanks,<br>
-Alex<br>
<br>
<br>
[0] <a href="http://git.openstack.org/cgit/openstack/tripleo-specs/tree/specs/policy/bug-tagging.rst#n30" rel="noreferrer" target="_blank">http://git.openstack.org/cgit/<wbr>openstack/tripleo-specs/tree/s<wbr>pecs/policy/bug-tagging.rst#n3<wbr>0</a><br>
[1] <a href="https://git.openstack.org/cgit/openstack/tripleo-quickstart/tree/doc/source/feature-configuration.rst#n21" rel="noreferrer" target="_blank">https://git.openstack.org/cgit<wbr>/openstack/tripleo-quickstart/<wbr>tree/doc/source/feature-<wbr>configuration.rst#n21</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks<br>
<br>
[1] <a href="https://bugs.launchpad.net/tripleo/+manage-official-tags" rel="noreferrer" target="_blank">https://bugs.launchpad.net/tri<wbr>pleo/+manage-official-tags</a><br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div>Rafael Folco<br></div>Senior Software Engineer<br></div></div>
</div>