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

updated bug reporting document to reflect the changes in the templates. #3445

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

enekofb
Copy link
Contributor

@enekofb enekofb commented Oct 4, 2023

What changed?

  • Updated bug reporting doc to reflect the change of having a single bug issue template
  • Open the conversation on how PM wants to handle this triage.

Why was this change made?
Update docs given we no longer have three bug issue templates.

@enekofb enekofb added the exclude from release notes Use this label to exclude a PR from the release notes label Oct 4, 2023
1) Bugs reported during the Acceptance Testing of a new feature/story. And by Acceptance Testing we mean manually testing a new feature to verify that it complies with the acceptance criteria, design, and behaves as expected before merging this feature into `main`. Those bugs are labeled with `bug_acceptance`. For reporting those bugs, `Acceptance Testing Bug Report` issue template can be used.
1. Raise a [new bug](https://github.com/weaveworks/weave-gitops-enterprise/issues/new/choose) via [`bug`](../.github/ISSUE_TEMPLATE/bug.md) issue template.
2. Fill-in the details about the bug, expected behaviour, etc ... Use the comments in the template to guide you through.
3. Once submitted, it will be labelled for [team/product-management](https://github.com/orgs/weaveworks/teams/product-management) to triage.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@weaveworks/product-management :

  1. what do you think about the steps here for bug issues created directly in this repo?
  2. would be labelling enough for us to take over or we want to get them assigned to us?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's fair to say that we automatically tag them as "pending" or something, and that way we can review "pending" issues and decide what to do with them?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exclude from release notes Use this label to exclude a PR from the release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants