Skip to content
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

Open
Tracked by #36675
mx-psi opened this issue Dec 4, 2024 · 6 comments · May be fixed by #36975
Open
Tracked by #36675

Define states an issue can be at #36677

mx-psi opened this issue Dec 4, 2024 · 6 comments · May be fixed by #36975
Assignees

Comments

@mx-psi
Copy link
Member

mx-psi commented Dec 4, 2024

An issue can currently be in a number of states:

  • Waiting for feedback from the community
  • Waiting for the author to provide more details
  • Waiting for codeowners to fix a bug
  • Waiting for somebody to come and implement the change
  • Blocked by something else
  • ...

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.

@VihasMakwana
Copy link
Contributor

I'll work on creating a diagram.

@VihasMakwana
Copy link
Contributor

@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?
Untitled-2024-10-29-0400

@pjanotti
Copy link
Contributor

pjanotti commented Dec 12, 2024

Thanks @VihasMakwana, nice. One suggestion:

  1. "Able to reproduce?" this can be a costly operation for the triagers, the codeowners should be in much better position to actually try the repro. My suggestion would be to say something like "Has good repro steps and/or description?" with the edge below being labeled "No/need more details"

@VihasMakwana
Copy link
Contributor

That makes sense to me. Thanks for taking a look!

@mx-psi
Copy link
Member Author

mx-psi commented Dec 16, 2024

@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?

@VihasMakwana
Copy link
Contributor

@mx-psi once you're back from holidays, please take a look at #36975

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants