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

update triage docs: needs-triage, p3 crashes/freezes #16113

Merged
merged 1 commit into from
Feb 1, 2024
Merged

Conversation

seanbudd
Copy link
Member

Adds information about the "needs-triage" label.

Adds a classification for P3s: a crash/freeze that affects only one user

@seanbudd seanbudd requested review from a team as code owners January 30, 2024 23:14
@seanbudd seanbudd changed the title update triage docs update triage docs: needs-triage, p3 crashes/freezes Jan 30, 2024
@seanbudd seanbudd added the conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review. label Jan 31, 2024
For controversial changes, a product decision from NV Access may be required before applying the `triaged` label. This can be indicated with adding the label `blocked/needs-product-decision`.
An issue with a simple solution should get labelled `good first issue`.
If it is a complex issue, technical investigation may be required.
This can be indicated with adding the label `blocked/needs-technical-investigation`.

### Priority
Bugs/regressions are given priorities based on an estimate of their severity and impact.
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it worth mentioning in L164 that P1s can also be a patch release? Are they considered milestones?

Copy link
Member Author

Choose a reason for hiding this comment

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

I don't think it's worthwhile documenting this. Sometimes we create milestones for patch releases, particularly when there are multiple issues involved

@gerald-hartig
Copy link
Collaborator

I like the improvements. Nice work.

Copy link
Member

@Qchristensen Qchristensen left a comment

Choose a reason for hiding this comment

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

Reads well, good work.

@seanbudd seanbudd merged commit 916b3c9 into master Feb 1, 2024
3 checks passed
@seanbudd seanbudd deleted the triageDocs branch February 1, 2024 03:14
@nvaccessAuto nvaccessAuto added this to the 2024.2 milestone Feb 1, 2024
Nael-Sayegh pushed a commit to Nael-Sayegh/nvda that referenced this pull request Feb 15, 2024
Adds information about the "needs-triage" label.

Adds a classification for P3s: a crash/freeze that affects only one user
SaschaCowley pushed a commit to SaschaCowley/nvda that referenced this pull request Feb 27, 2024
Adds information about the "needs-triage" label.

Adds a classification for P3s: a crash/freeze that affects only one user
Adriani90 pushed a commit to Adriani90/nvda that referenced this pull request Mar 13, 2024
Adds information about the "needs-triage" label.

Adds a classification for P3s: a crash/freeze that affects only one user
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
conceptApproved Similar 'triaged' for issues, PR accepted in theory, implementation needs review.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants