[kata-dev] Plan for organizing the kata issue backlog

Ariel Adam aadam at redhat.com
Mon Aug 10 17:19:25 UTC 2020


Hi everyone.
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 *buckets*
and a proposed plan to work on these buckets.

Overall there are currently 1,019 open issues
<https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+sort%3Arepository+>
.
Out of these there are 106 open issues with attached PRs
<https://github.com/issues?page=1&q=is%3Aissue+is%3Aopen+org%3Akata-containers+linked%3Apr+sort%3Arepository>
and
as Christophe suggested, these issues will be moved into an in-progress on
the issue backlog board
<https://github.com/orgs/kata-containers/projects/23> and will not be part
of our backlog grooming work.

Looking at the remaining issues we propose to split them as follows:

   - Issues opened this year (333 open issues
   <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+>)
   and everything else (686 open issues
   <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3C%3D2020-01-01+>
   )
   - Another split of issues opened this year which are bugs (112 open
   issues
   <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+label%3Abug+-linked%3Apr+sort%3Arepository+>)
   and not bugs (174 open issues
   <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+-label%3Abug+-linked%3Apr+sort%3Arepository+>
   )
   - For not bugs splitting to kata-2.0-features (45 open issues
   <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+>)
   and not (129 open issues
   <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+>
   )
   - Once we finish with this years issues we will move on to handle the
   previous year issues

*Our proposed approach is as following:*

   - 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
   - For each issue reviewed the reviewer should check if that issue can be
   closed (duplicate, not relevant, etc...) or is a valid issue
   - 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)
   - 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

*Propose timeframe:*

   - 2nd week of August - issues opened this year which are not bugs and
   are labeled kata-2.0-features (45 open issues
   <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+>
   )
   - 3rd week of August - issues opened this year which are bugs (112 open
   issues
   <https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+created%3A%3E2020-01-01+label%3Abug+-linked%3Apr+sort%3Arepository+>
   )
   - 4th week of August - issues opened this year which are not bugs and
   are not labeled kata-2.0-features (129 open issues
   <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+>
   )
   - 1st week of September - starting to work on issues from previous years
   depending on our progress

Let us know if this plan makes sense, if you have comments or other
suggestions.

Thanks.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.katacontainers.io/pipermail/kata-dev/attachments/20200810/549d8958/attachment-0001.html>


More information about the kata-dev mailing list