Skip to content

Commit

Permalink
Add triage policy (#776)
Browse files Browse the repository at this point in the history
  • Loading branch information
dtivel authored Oct 22, 2024
1 parent fcf32ac commit 96dff81
Show file tree
Hide file tree
Showing 2 changed files with 42 additions and 0 deletions.
4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -109,3 +109,7 @@ At this time, only RSA PKCS #1 v1.5 is supported.
ECDSA is not supported. Not only do some signature providers not support ECDSA, [the Microsoft Trusted Root Program does not support ECDSA code signing.](https://learn.microsoft.com/security/trusted-root/program-requirements#b-signature-requirements)

> **Please Note**: Signatures using elliptical curve cryptography (ECC), such as ECDSA, aren't supported in Windows and newer Windows security features. Users utilizing these algorithms and certificates will face various errors and potential security risks. The Microsoft Trusted Root Program recommends that ECC/ECDSA certificates shouldn't be issued to subscribers due to this known incompatibility and risk.
## Useful Links

* [Issue Triage Policy](triage-policy.md)
38 changes: 38 additions & 0 deletions triage-policy.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
# Issue Triage Policy

This policy aims to ensure that issues are handled efficiently and transparently, keeping the project on track and maintaining a high level of community engagement.

For reporting security vulnerabilities, follow [this guidance](SECURITY.md).

## Categorize Issues

* **Bugs**: issues that describe a malfunction or unintended behavior
* **Feature Requests**: suggestions for new features or enhancements
* **Documentation**: issues related to missing or unclear documentation
* **Questions**: general inquiries or requests for clarification

## Prioritize Issues

* **Priority 0 (P0)**: cannot release without addressing
* **Priority 1 (P1)**: blocking core scenarios, regressions, or high-impact issues affecting many users
* **Priority 2 (P2)**: important but not blocking, such as feature requests with significant community interest
* **Priority 3 (P3)**: low-impact issues, minor bugs, or enhancements with limited scope

## Label Issues

* Use labels to indicate the type and priority of the issue (e.g.: [bug](https://github.com/dotnet/sign/labels/bug), [feature-request](https://github.com/dotnet/sign/labels/feature-request), [Priority:1](https://github.com/dotnet/sign/labels/Priority%3A1), [Priority:2](https://github.com/dotnet/sign/labels/Priority%3A2)).
* Additional labels can be used for specific areas of the project (e.g., CLI, documentation).

## Review and Update

* Conduct triage meetings (typically weekly, except in December) to review new issues and update the status of existing ones.
* If more information is needed from the community, the issue will be labelled with [needs-more-info](https://github.com/dotnet/sign/labels/needs-more-info) and awaited.
* If information is needed from the issue author and the author has not responded within 14 days, the issue will be closed but can be reactivated when information is available.

## Triage Outcome

A triaged issue should fall into one of these states:

* a priority has been assigned and the issue is in the backlog
* the issue is labeled with needs-more-info and is waiting on user response
* the issue is closed (e.g.: question immediately answered)

0 comments on commit 96dff81

Please sign in to comment.