-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Define states an issue can be at #36677
Comments
I'll work on creating a diagram. |
@mx-psi I prepared a high level diagram with labels at different stages. I know I'm missing some labels but this gives us a good starting point. Please let me know how you feel about it? |
Thanks @VihasMakwana, nice. One suggestion:
|
That makes sense to me. Thanks for taking a look! |
@VihasMakwana This makes sense to me, thanks for working on it! I think I would probably leave out the 'release blocker' and the 'New component' parts of the diagram (they feel like issue types more than states that any issue can potentially be at). Could you file a PR to add this to https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/issue-triaging.md? So that the diagram is easy to edit, could you use Mermaid so that we can edit the diagram over time? |
An issue can currently be in a number of states:
It would be useful to have a list of said states in the issue triaging document and a state diagram of how issues can move through these.
The text was updated successfully, but these errors were encountered: