Open Capstan opened 6 years ago
This is really developer experience - but we don't have a separate team for that yet. I'm inclined to say yes to the concept, but no to this implementation. When we start doing automation for issues and PR response time and nagging, we could provide this in that dashboard. What I want to prevent is a large amount of label proliferation.
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 2.5 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team (@bazelbuild/triage
) if you think this issue is still relevant or you are interested in getting the issue resolved.
@meteorcloudy FYI
This is a suggestion to improve the release automation to make it very obvious when a given accepted pull request will be available by using labels to mark said pull requests. Specifically, it's a suggestion to do the following:
in-candidate-0.8rc00
in-release-0.8
in-candidate-0.8*
within-release-0.8
in-candidate-0.8*
labels.This could similarly be applied to issues fixed by commits in the release.
Some additional maintenance might be required, e.g., if a release is abandoned, may have to remove
in-candidate-
labels, or if a commit is later rolled-back, not sure how to have the system know not to apply that label.