<div dir="ltr"><div dir="ltr">Like ships that cross in the night... :)</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 23, 2020 at 8:11 AM Tatiana Tereshchenko <<a href="mailto:ttereshc@redhat.com">ttereshc@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 dir="ltr"><div>Grant, thanks for trying to solve it thoroughly and with less bookkeeping work for others.</div><div><br></div>However, I agree with the sentiment that it's better to have no milestone than the wrong one.<div>Setting a milestone correctly is a difficult-to-impossible task, since that can change with time. Also some projects/plugins assign milestones as a part of release process, some assign ahead of time.<div><div><div><br></div><div>How about every mini-team, pulpcore and plugins, will figure out milestones themselves and set them whenever they think is necessary?</div><div>And for now we just:</div><div><ul><li>create a Katello tag</li><li>set this tag for all Katello items</li><li>adjust priority (P1 - High, P2 - Normal, P3 - low)</li><li>remove Katello-Px tags</li></ul><div>What do you all think?</div></div></div></div></div></div></blockquote><div><br></div><div>See the proposal I sent like 2 seconds before I saw you had replied! I think we're in broad agreement, but I like mine better :)</div><div><br></div><div>G</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 23, 2020 at 12:30 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@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 dir="ltr">pulpcore is not the only project with milestones. Each project has its own set of milestones to represent different versions. The issue is your proposal is trying to assign all Katello-PX issues to a pulpcore milestone. That won't work if you have say a pulp_container or pulp_ansible issue with a Katello-PX tag. <div><br></div><div>You could go through all the Katello-PX issues and try to figure out which milestone in which project to assign it to but with so many milestones and projects, it's going to be a huge pain. My suggestion was to just worry about the open issues and not try to retroactively assign these issues to milestones.<br clear="all"><div><div dir="ltr"><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></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 7:12 PM Grant Gainey <<a href="mailto:ggainey@redhat.com" target="_blank">ggainey@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 dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 6:17 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@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 dir="ltr">A couple observations: the 3.3[0] and 3.4[1] milestones already exist in redmine. Also, you won't be able to assign any of the MODIFIED issues to 3.3 because they're all plugin issues and the 3.3 milestone is exclusive to pulpcore. IMHO, I probably wouldn't assign any issues to any milestones. I think it would be worse having an issue on the wrong milestone than it being unassigned.</div></blockquote><div><br></div><div>If pulpcore is the only thing that has the version-milestones, then we're at a dead stop. The whole point of the initial process proposal, was that "milestone" would be able to completely replace the Katello-PX tags as a way for Katello to tell us what they needed/expected when; if that's only useful for pulpcore, then we have missed the mark, since the tags are used cross-organizationally.</div><div><br></div><div>If you look at the <a href="https://pulp.plan.io/issues?c%5B%5D=project&c%5B%5D=tracker&c%5B%5D=status&c%5B%5D=priority&c%5B%5D=subject&c%5B%5D=author&c%5B%5D=assigned_to&c%5B%5D=cf_3&c%5B%5D=cf_7&f%5B%5D=status_id&f%5B%5D=cf_7&f%5B%5D=&group_by=&op%5Bcf_7%5D=%3D&op%5Bstatus_id%5D=o&set_filter=1&sort=project%2Cstatus%2Ccf_7&t%5B%5D=&utf8=%E2%9C%93&v%5Bcf_7%5D%5B%5D=Katello-P1&v%5Bcf_7%5D%5B%5D=Katello-P2&v%5Bcf_7%5D%5B%5D=Katello-P3" target="_blank">list of open-issues</a> currently tagged with Katello-PX tags, you'll see more than pulpcore in there.</div><div><br></div><div>From ttereshc's summary email:</div><div><div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><ul><li style="margin-left:15px">tag katello-related issues as 'Katello'</li></ul><ul><span><li style="margin-left:15px"><b><font color="#000000">use the milestone field to define the planned-pulp-release-version</font></b></li></span></ul><ul><li style="margin-left:15px">use the Priority field to mark how important it is *to Katello*</li></ul><ul><li style="margin-left:15px">remove the existing Katello P1/2/3 tags</li></ul></blockquote></div></div><div> If we can't mark non-pulpcore-issues with "planned-pulp-release-version", then this proposal is DOA.</div><div><br></div><div>Clearly, we need some more discussion! Anyone else want to join in?</div><div><br></div><div>G</div><div><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 dir="ltr"><div><br></div><div>That would leave the process somewhat simpler:</div><div><br></div><div>1. Create a Katello tag and assign it to all Katello-PX issues</div><div>2. Set the priority to high for P1 issues, medium for P2 issues, and low for P3 issues</div><div>3. Optionally, add open P2 issues to 3.4 milestone</div><div>4. Remove all Katello-PX tags</div><div><br></div><div>And then Katello can just add the 15 issues at NEW/ASSIGNED to a milestone as they see fit: <a href="https://pulp.plan.io/issues?query_id=113" target="_blank">https://pulp.plan.io/issues?query_id=113</a>.</div><div><br></div><div>[0] <a href="https://pulp.plan.io/versions/83" target="_blank">https://pulp.plan.io/versions/83</a></div><div>[1] <a href="https://pulp.plan.io/versions/88" target="_blank">https://pulp.plan.io/versions/88</a></div><div><div><div dir="ltr"><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></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 22, 2020 at 5:15 PM Grant Gainey <<a href="mailto:ggainey@redhat.com" target="_blank">ggainey@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 dir="ltr"><div>Hey folks,</div><div><br></div><div>To close the loop on this:</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 9, 2020 at 6:26 AM Tatiana Tereshchenko <<a href="mailto:ttereshc@redhat.com" target="_blank">ttereshc@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 dir="ltr">+1 and to the nitpick as well<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*</li><li>remove the existing Katello P1/2/3 tags</li></ul></div></div></div></blockquote><div>I am working to actually make these changes, and need a quick check on specifics.</div><div><br></div><div>Right now there are 29 open issues with a Katello-PX tag. 14 of these are in MODIFIED/P1, all against various plugins (ansible, certguard, and rpm) I propose to do the following (order matters):</div><div><ol><li>create milestones for <b>pulp-3.0</b>, <b>pulp-3.4</b>, <b>pulp-3.5</b>, and <b>pulp-3.6</b> (thinking both ahead and behind a little)</li><li>create a <b>Katello</b> tag</li><li>anything in MODIFIED gets the <b>3.3</b> milestone.</li><li>Remaining open katello-P2 issues get a <b>3.4</b> milestone.</li><li>Remaining open katello-P3 issues get a <b>3.5</b> milestone</li><li>open <b>Katello-P1</b> issues get a <b>High</b> priority</li><li>all other open issues get a <b>Normal</b> priority</li><li>closed Katello-PX issues get the <b>3.0 </b>milestone</li><li>tag all Katello-PX issues, open or closed, with <b>Katello</b> </li><li>remove all Katello-PX tags on anything open or closed</li><li>This will leave us with 29 open issues using the new process, <b>which will need Priority and Milestone triage</b></li></ol></div><div>Does that catch everything we want from this, going forward? I'd like a quick turnaround here so we can make sure we are working on 3.4 items in the right order.</div><div><br></div><div>G</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 8, 2020 at 6:47 PM David Davis <<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@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 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"><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>
_______________________________________________<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>
_______________________________________________<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><br clear="all"><div><br></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>
_______________________________________________<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>
</blockquote></div><br clear="all"><div><br></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>
</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>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><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>