Ariel,
On Sun, Dec 13, 2020 at 2:37 PM Ariel Adam <aadam@redhat.com> wrote:
Hi everyone. A kind reminder to review your open issues and tag them with labels from area/* (area/api, area/cli, area/config, area/documentation, area/logging, area/networking, area/performance, area/storage, area/tracing, area/packaging etc...) so we can start grouping them and tracking them from a higher level.
Considering the plan of deprecating 1.x on May 12th 2021 (see http://lists.katacontainers.io/pipermail/kata-dev/2020-November/001601.html), and with a considerable amount of the open issues being related to 1.x (around a third of them), I'd like to ask whether we could, instead of pointing to all the issues and have people digging there, start from: * kata-containers/kata-containers, as this is the way we, Kata Community, is moving forward; * kata-containers/tests, as this is a must for the project; * kata-containers/community, as it doesn't change with the deprecation; * kata-containers/documentation, same as above; This may give an incentive, as the labeling work will be focusing on the future. And would reduce the amount of issues to take a look from 325[0] to 222[1]. Another idea to consider is going through the repos that were not merged into kata-containers/kata-containers and cleaning up the issues there, in a way we clearly could evaluate what's 2.x related. Also, maybe it's time to consider having automated work to add a comment in the 1.x issues saying for those who opened them to verify if they still face the same issues on 2.x and, if so, open an issue there instead? What do you think? [...] [0] Search as it's Today: https://github.com/issues?q=is%3Aissue+is%3Aopen+org%3Akata-containers+creat... [1] Suggested search: https://github.com/issues?q=is%3Aissue+is%3Aopen+repo%3Akata-containers%2Fka... Best Regards, -- Fabiano Fidêncio