<div dir="ltr">SGTM - thanks for driving this!</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 10, 2020 at 10:20 AM Ariel Adam <<a href="mailto:aadam@redhat.com">aadam@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Hi everyone.</div><div>As part of the work we are doing to reduce and organize the issue backlog we have thought about a potential split of the open issues into <b>buckets</b> and a proposed plan to work on these buckets.</div><div><br></div><div>Overall there are currently <a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+sort%3Arepository+" target="_blank">1,019 open issues</a>.</div><div>Out of these there are <a href="https://github.com/issues?page=1&q=is%3Aissue+is%3Aopen+org%3Akata-containers+linked%3Apr+sort%3Arepository" target="_blank">106 open issues with attached PRs</a> and as Christophe suggested, these issues will be moved into an in-progress on the <a href="https://github.com/orgs/kata-containers/projects/23" target="_blank">issue backlog board</a> and will not be part of our backlog grooming work. </div><div><br></div><div>Looking at the remaining issues we propose to split them as follows:</div><div><ul><li style="margin-left:15px">Issues opened this year (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+" target="_blank">333 open issues</a>) and everything else (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3C%3D2020-01-01+" target="_blank">686 open issues</a>)</li><li style="margin-left:15px">Another split of issues opened this year which are bugs (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+label%3Abug+-linked%3Apr+sort%3Arepository+" target="_blank">112 open issues</a>) and not bugs (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+-linked%3Apr+sort%3Arepository+" target="_blank">174 open issues</a>)</li><li style="margin-left:15px">For not bugs splitting to kata-2.0-features (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+label%3Akata-2.0-features+-linked%3Apr+sort%3Arepository+" target="_blank">45 open issues</a>) and not (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+-label%3Akata-2.0-features+-linked%3Apr+sort%3Arepository+" target="_blank">129 open issues</a>)</li><li style="margin-left:15px">Once we finish with this years issues we will move on to handle the previous year issues</li></ul><div><b>Our proposed approach is as following:</b></div></div><div><ul><li style="margin-left:15px">Every week we will focus as a community on one of the buckets and will also use the bi-monthly backlog review meetings to help focus</li><li style="margin-left:15px">For each issue reviewed the reviewer should check if that issue can be closed (duplicate, not relevant, etc...) or is a valid issue</li><li style="margin-left:15px">If you believe this is a valid issue remove the "needs-review" label to indicate the issue has been triaged (or ping James/me to to do it) </li><li style="margin-left:15px">Later on once we have finished with reviewing the issue backlog we can then move on to decide on adding new labels (such as MVP) and removing/joining old labels</li></ul></div><div><b>Propose timeframe:</b></div><div><ul><li style="margin-left:15px">2nd week of August - issues opened this year which are not bugs and are labeled kata-2.0-features (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+label%3Akata-2.0-features+-linked%3Apr+sort%3Arepository+" target="_blank">45 open issues</a>)<br></li><li style="margin-left:15px">3rd week of August - issues opened this year which are bugs (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+label%3Abug+-linked%3Apr+sort%3Arepository+" target="_blank">112 open issues</a>)</li><li style="margin-left:15px">4th week of August - issues opened this year which are not bugs and are not labeled kata-2.0-features (<a href="https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+-label%3Akata-2.0-features+-linked%3Apr+sort%3Arepository+" target="_blank">129 open issues</a>)</li><li style="margin-left:15px">1st week of September - starting to work on issues from previous years depending on our progress</li></ul></div><div>Let us know if this plan makes sense, if you have comments or other suggestions.</div><div><br></div><div>Thanks. </div><div><br></div><div><br></div></div>
_______________________________________________<br>
kata-dev mailing list<br>
<a href="mailto:kata-dev@lists.katacontainers.io" target="_blank">kata-dev@lists.katacontainers.io</a><br>
<a href="http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev" rel="noreferrer" target="_blank">http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev</a><br>
</blockquote></div>