Thanks for the help! I should have linked to it to temp everyone to click: https://github.com/apache/beam/issues?q=is%3Aissue+is%3Aopen+label%3A%22awaiting+triage%22
Kenn On Mon, Oct 31, 2022 at 1:30 PM Yi Hu via dev <dev@beam.apache.org> wrote: > up to 120, my bad > > On Mon, Oct 31, 2022 at 4:29 PM Yi Hu <ya...@google.com> wrote: > >> Thanks for raising this. Also closed a couple of issues. Now the number >> is up to 12. >> >> On Mon, Oct 31, 2022 at 9:24 AM Manu Zhang <owenzhang1...@gmail.com> >> wrote: >> >>> I closed several issues that have already been fixed. It looks we didn’t >>> reference the issue number in commit message which can auto-close the issue. >>> >>> Kenneth Knowles <k...@apache.org>于2022年10月31日 周一20:01写道： >>> >>>> Hi all >>>> >>>> We have built up to 138 GitHub Issues with the "awaiting triage" label. >>>> If you can, take just a couple minutes today to grab a couple and triage >>>> them: >>>> >>>> - get the right priority label ( >>>> https://beam.apache.org/contribute/issue-priorities/) >>>> - get the right component label (runner, IO, SDK, etc) >>>> - ping someone who may be interested >>>> - remember to remove the "awaiting triage" label >>>> >>>> It really is pretty quick! >>>> >>>> Kenn >>>> >>>
