It's no secret that the handling of issues & PRs hasn't been ideal. There are only so many hours in a day, and plenty of work on engineers' plates keeping them busy.
We are working to correct this. We've allocated specific resources dedicated to the triage and tracking process. That team is still coming up to speed, so it will take a bit of time to fully see their impact.
Initially, the team will focus on issues. This includes common triage tasks like ensuring the necessary information has been included, routing the issue correctly, and most importantly prioritization. Over time, the team is looking to take on verifying bug replication and potentially providing fixes on their own.
The other aspect they are focusing on is reducing the number of unanswered issues in the queue. Over the next few weeks, the team will be doing a comprehensive review of the existing untriaged or unanswered issues.
In some instances, these issues may be old and potentially out of date, either because a fix/workaround was found or the initially reported problem is no longer relevant. In those cases, the team will ask for a confirmation on whether or not the issue still needs resolution, and then close the issue if possible. We want to clean up the open backlog, but we also want to make sure we don’t lose anything that is still valid in the process.
To start, the team will specifically focus on the bazelbuild/bazel repository. Over time, we’re looking to include other repositories for specific rule sets or plugins.
Once the team has gotten up to speed, we’re looking to have them work on the PR process as well. I’ll have more information on that when we get to that point. In the meantime, please feel free to reach out to me if you have any questions or concerns. I’m happy to hop on a quick call to get to know members of the community and better understand your concerns.
Thanks :)
Jason Dobies
--
You received this message because you are subscribed to the Google Groups "bazel-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bazel-discus...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bazel-discuss/CAFDVkYH0Qq4bKWTAsCpwWaE1eybQ4i5F%2B7%2BC3DosL2Ocrp9z5A%40mail.gmail.com.
|