<div dir="ltr">Nitpick but I would use 'Katello' to be consistent with other tags. And agreed that we should remove the Katello P tags. Other than that, LGTM.<br clear="all"><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>David</div></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 8, 2020 at 12:42 PM Justin Sherrill <<a href="mailto:jsherril@redhat.com" target="_blank">jsherril@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>+1 to all of this!<br>
</p>
<div>On 4/8/20 12:35 PM, Brian Bouterse
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">
<div>Thanks for writing this up and sending! My only addition
would be to also remove the P1, P2, P3 tags entirely after
setting all tagged issues with 'katello' and setting their
priorities based on the previous P1/P2/P3 label.</div>
<div><br>
</div>
<div>Thank you!<br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Apr 8, 2020 at 12:32
PM Grant Gainey <<a href="mailto:ggainey@redhat.com" target="_blank">ggainey@redhat.com</a>> wrote:<br>
</div>
<blockquote class="gmail_quote">
<div dir="ltr">Hey folks,
<div><br>
</div>
<div>As part of working with the katello upstream, we have
been using a mechanism for prioritizing pulp-issues in
order to help keep the Katello Gang unblocked. We have
been using the 'Tags' field in an issue, and marking
things as Katello-P1/2/3, with P1 being "blocker for the
next release".</div>
<div><br>
</div>
<div>As we move through releases, this is starting to
break down - last release's P2 is this release's P1.
This was brought up for discussion in today's
integration meeting.</div>
<div><br>
</div>
<div>In order to continue being able to prioritize work,
we're proposing a change to the process to make it more
sustainable as releases go on. I *think* I have captured
the proposal effectively below - if I've missed
something vital, I'm sure someone who was in the meeting
will expand on it:</div>
<div>
<ul>
<li>tag katello-related issues as 'katello'</li>
<li>use the milestone field to define the
planned-pulp-release-version</li>
<li>use the Priority field to mark how important it
is, *to katello*, to fix a bug NOW, as opposed to
'the day before the release is cut' (which in
practice is likely to be 'blockers are critical,
everything else is normal')</li>
</ul>
<div>This will make it easy to query redmine in a way
that returns a properly-ordered list, without some
human having to go through and group-change tags on
multiple issues at once.</div>
</div>
<div><br>
</div>
<div>Would appreciate more eyes on this, and especially
input on what I might have missed. We'd like to switch
'soon', so feedback before, say next Wednesday 15-APR
would be great!</div>
<div><br>
</div>
<div>Thanks,</div>
<div>G</div>
<div>-- <br>
<div dir="ltr">
<div dir="ltr">
<div>
<div dir="ltr">
<div>Grant Gainey</div>
<div>Principal Software Engineer, Red Hat System
Management Engineering</div>
</div>
</div>
</div>
</div>
</div>
</div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote>
</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Pulp-dev mailing list
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>