<div dir="ltr">I'd be OK with using time last edited or created being over some value (6 months) as an auto-close with a note to re-open. For older bug reports or feature requests - if a user has lived without it for a long time without contributing a fix, then some re-engagement to re-open an issue helps provide some priority assessment.<div><br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-family:RedHatText,sans-serif">
Robin Chan<span style="color:rgb(170,170,170);margin:0px;font-size:14px"></span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;text-transform:capitalize;font-family:RedHatText,sans-serif">She/Her/Hers</p>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
<span>Satellite Software Engineering Manager - Pulp</span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;font-family:RedHatText,sans-serif">
<a style="color:rgb(0,136,206);margin:0px;text-decoration:none;font-family:RedHatText,sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span></span></a>
</p>
<div style="margin-bottom:4px">
</div>
<p style="font-weight:normal;margin:0px;font-family:RedHatText,sans-serif">
IRC: rchan
</p><p style="margin:0px;font-family:RedHatText,sans-serif"><span style="color:rgb(0,0,0);font-family:Overpass,"Helvetica Neue",Helvetica,Arial,"Lucida Grande",sans-serif">Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours.</span><span style="font-weight:normal;font-size:12px"><span><br></span></span></p>
<div style="margin-top:12px">
<table border="0">
<tbody><tr>
<td width="100px"><a href="https://www.redhat.com" target="_blank"> <img src="https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" width="90" height="auto"></a> </td>
</tr>
</tbody></table>
</div>
</div><div><br></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 7, 2020 at 11:34 AM David Davis <<a href="mailto:daviddavis@redhat.com">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">After open floor, the consensus was to give all users the ability to reopen issues aside from dupes or completed/released. I've done that.<div><br></div><div>I think we want to go through open issues and close them out or groom them regardless of what we decide about doing a mass close so I went ahead and added an agenda item to our pulpcore meeting.<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 Fri, Aug 7, 2020 at 10:49 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 to allow all users to re-open issues.<div>If ^, then +1 to closing as many backlog issues as seems needed.</div><div><br></div><div>We can close based on the date and then review manually items with redmine issue number less than N - old ones, to see if they have recent comments or just spam.</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 6, 2020 at 6:08 PM Ina Panova <<a href="mailto:ipanova@redhat.com" target="_blank">ipanova@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 clear="all"><div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><br><br>--------<br>Regards,<br><br>Ina Panova<br>Senior Software Engineer| Pulp| Red Hat Inc.<br><br>"Do not go where the path may lead,<br> go instead where there is no path and leave a trail."<br></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Aug 5, 2020 at 8:54 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">We've been discussing the possibility of closing issues in redmine due to the overwhelming number of issues at NEW. Currently, we have 930 issues at NEW and I think that exceeds our capacity to address each issue individually.<div><br></div><div>The first item I want to bring up for discussion is expanding the ability for users to reopen closed issues. Currently only authors can reopen issues at CLOSED excluding CLOSED - DUPLICATE and CLOSED - COMPLETE. Should we expand this to all redmine users?</div></div></blockquote><div> </div><div>+1 to expand it to all users.<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>If we expand this permission, this should give us the ability to safely close out issues that fit some criteria. I looked at the pulpcore issues and limited the issues to just ones without a Katello tag or a BZ and that were created before 2020[0]. This still leaves us with almost 300 NEW issues in pulpcore which still seems unrealistic to go through. Any thoughts on what criteria to use?</div></div></blockquote><div> </div><div>We could also exclude issues that have Pulp2 tag.</div><div>Even if we end up having 300 issues to process, I know that sounds a lot, but we can regularly dedicate 5 mins(timeboxed!) of our pulpcore team meeting, or open floor to go through. For some issues it is enough to read the title to make a decision. <br></div><div>I *think* this might be a feasible idea, look how many and good improvements we did in redmine having it on the agenda for each open floor.</div><div><br></div><div>Alsom, what will be the state of the issues we are going to mass close - CLOSED-WON'TFIX? <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>[0] It would be better to use updated at to scope issues but unfortunately a lot of older issues have been updated recently due to spam comment</div></div></blockquote><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><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></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>
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>
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>