Previously, we had automation that would automatically mark self-assigned self-reported issues as triaged. That is probably a third of issues or more. I'm not sure what else. I appreciate Valentyn keeping an eye on the Python label. One issue is that a lot of triage work is getting the labels right (a lot of things end up in beam-model or beam-community)
Kenn On Mon, Dec 5, 2022 at 6:23 AM Kerry Donny-Clark via dev < dev@beam.apache.org> wrote: > This is a glorious achievement Kenn! To keep things clean going forward > are there any improvements we can make in our issue creation flow? > > On Fri, Dec 2, 2022, 6:44 PM Kenneth Knowles <k...@apache.org> wrote: > >> Hi all, >> >> I've finally done it! I've emptied the label "awaiting triage". Help me >> keep it that way! This ensures that we actually at least *look* at each >> issue once, preferably soon after it is filed. The idea is that you make >> sure the priority and other labels are right, since users are not expected >> to know how we use labels. >> >> >> https://github.com/apache/beam/issues?q=is%3Aissue+is%3Aopen+label%3A%22awaiting+triage%22 >> >> Kenn >> >
