<font face="Default Sans Serif,Verdana,Arial,Helvetica,sans-serif" size="2"><div><div><br></div></div>>Hi everyone.<br>>James and I have been discussing this and we figured it would make<br>>sense to use next week's Tuesday's backlog review meeting to identify<br>>15-20 PRs which are a MUST for the release and focus on them.<br>><br>>Obviously that's on top of people reviewing the huge pool of PRs. <br>><br>>Any objections to this idea?<br><br><div>This makes sense. In the meantime we'll keep reviewing as much as we can before Tuesday to bring down the overall backlog.</div><div><br></div><div>Thanks,</div><div>Pradipta</div><div><br></div><div>><br>>Thanks. <br>>On Thu, Sep 24, 2020 at 11:11 AM Hunt, James O<br>><<a href="mailto:james.o.hunt@intel.com" target="_blank">james.o.hunt@intel.com</a>> wrote:<br>>Hi All,<br>> <br>> # TL;DR<br>> <br>> Please start commenting on the PRs in [1].<br>> <br>> <br>> # A plea<br>> <br>> We currently have 115 open PRs [1]. That figure *excludes* the<br>>do-not-merge / wip ones! It's great that the project is seeing so<br>>much activity, but here we hit a bottleneck...<br>> <br>> We have one hundred and fifteen bug fixes and features that have not<br>>landed and *cannot* land until they have been reviewed and<br>>approved... by you! The project mandates these reviews and "acks",<br>>and for good reason. But until we get more review activity, all those<br>>bug fixes and features are "blocked". That's a big shame considering<br>>how much time and energy that has gone into creating the PRs, and how<br>>close we are to a major release!<br>> <br>> If you can spare some cycles, *please* take a look at the backlog<br>>[1] and help us to get these changes merged to make Kata better and<br>>keep the project momentum high.<br>> <br>> Never done this before? No problem - just dive in! Well, after<br>>you've taken a peek at [2] and [3]. You might also want to look at<br>>[4] for inspiration. Any problems - head for [5] ;)<br>> <br>> <br>> # An idea<br>> <br>> Could we identify a "Top 10" set of PRs each week that we will do<br>>everything possible to get landed? I'm sure everyone will have their<br>>own opinion of which PRs are important here. Maybe we could vote<br>>somehow? If we can implement this, I'd like to suggest that if you<br>>propose a "Top 10" PR, you would be expected to help out where<br>>possible getting that PR landed *and* helping with the outstanding<br>>backlog. Thoughts?<br>> <br>> Cheers,<br>> <br>> James<br>> <br>> [1] -<br>><a href="https://github.com/pulls?page=1&q=is%3Aopen+is%3Apr+org%3Akata-contai" target="_blank">https://github.com/pulls?page=1&q=is%3Aopen+is%3Apr+org%3Akata-contai</a><br>>ners+-label%3Ado-not-merge+-label%3Awip&utf8=%E2%9C%93<br>> [2] -<br>><a href="https://github.com/kata-containers/community/blob/master/CODE_OF_COND" target="_blank">https://github.com/kata-containers/community/blob/master/CODE_OF_COND</a><br>>UCT.md<br>> [3] -<br>><a href="https://github.com/kata-containers/community/blob/master/CONTRIBUTING" target="_blank">https://github.com/kata-containers/community/blob/master/CONTRIBUTING</a><br>>.md<br>> [4] -<br>><a href="https://github.com/kata-containers/community/blob/master/PR-Review-Gu" target="_blank">https://github.com/kata-containers/community/blob/master/PR-Review-Gu</a><br>>ide.md<br>> [5] -<br>><a href="https://github.com/kata-containers/community/blob/master/README.md#jo" target="_blank">https://github.com/kata-containers/community/blob/master/README.md#jo</a><br>>in-us<br>> <br>> ---<br>> <a href="https://katacontainers.io/" target="_blank">https://katacontainers.io/</a> | <a href="https://github.com/kata-containers" target="_blank">https://github.com/kata-containers</a><br>> Open Source Technology Center<br>> Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way,<br>>Swindon SN3 1RJ.<br>><br>>---------------------------------------------------------------------<br>> Intel Corporation (UK) Limited<br>> Registered No. 1134945 (England)<br>> Registered Office: Pipers Way, Swindon SN3 1RJ<br>> VAT No: 860 2173 47<br>> <br>> This e-mail and any attachments may contain confidential material<br>>for<br>> the sole use of the intended recipient(s). Any review or<br>>distribution<br>> by others is strictly prohibited. If you are not the intended<br>> recipient, please contact the sender and delete all copies.<br>> <br>> <br>> _______________________________________________<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" target="_blank">http://lists.katacontainers.io/cgi-bin/mailman/listinfo/kata-dev</a><br>> _______________________________________________<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="INVALID URI REMOVED" target="_blank">INVALID URI REMOVED</a><br>>ers.io_cgi-2Dbin_mailman_listinfo_kata-2Ddev&d=DwIGaQ&c=jf_iaSHvJObTb<br>>x-siA1ZOg&r=iUAhCfuapvQr9JhD2ekUEBDG6Qvg1dk2G3fa8l8Y4cE&m=YhZEKg7H6R6<br>>_5_EXoqhXNJM_QK_P7m5RzaE5oMwvV70&s=bsWJxVg4p6bckFPEsB5wJ7TvkQ0PcQp1AS<br>>pdl1UM9aY&e= <br>></div></font><BR>