languages/dart-sdk
languages/dart-sdk
1
0
Fork 0
mirror of https://github.com/dart-lang/sdk synced 2024-09-30 04:48:37 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update Triaging-Dart-SDK-issues.md

Browse source
This commit is contained in:
Devon Carew 2024-05-30 09:07:17 -07:00 committed by GitHub
parent be24c7942e
commit 315dad50da
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 21 additions and 28 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

49
docs/Triaging-Dart-SDK-issues.md
View file

@ -1,47 +1,41 @@
> [!IMPORTANT]
> This page was copied from https://github.com/dart-lang/sdk/wiki and needs review.
> Please [contribute](../CONTRIBUTING.md) changes to bring it up-to-date -
> removing this header - or send a CL to delete the file.
---
## Workflow
* Look through issues that don't have an area assigned.
* Use the [SDK triage query].
* Does the issue relate to code in the SDK?
* Assign to the right area by adding an `area-*` label. **Note: `area-language` is deprecated. New language issues should be [moved][move] to the [language repo](https://github.com/dart-lang/language).**
* Is the issue in `area-library`?
* Assign to the right area by adding an `area-*` label.
* Is the issue in `area-core-library`?
* Assign the right `library-*` label, too.
* Is it obvious if the issue is a bug or enhancement?
* Optional: Add `type-bug` or `type-enhancement` if you can.
* Does the issue relate to code in another `dart-lang` project/package?
* Move the issue to the right repo by using the `Transfer issue` link (between github orgs, use [`/move to ...`][move]).
* Move the issue to the right repo by using the `Transfer issue` link.
* Get emails when issues are tagged with labels you care about
* Use the [Dart SDK email tool].
## Issue Labels
### Priority
* Level of **team urgency**
* Should be the opinion of team and/or product management
* Can be affected by the quantity/priority of existing issues - *If everything is P0, nothing is P0*
* May evolve as other issues are resolved and new issues are opened
* Levels
* **[p0-critical][]**: Drop everything and fix it.
* For dev channel: blocks the release. Valid cherry-pick.
* For release channel: worthy of a "dot" release
* **[p1-high][]**: Planned for the in-progress release
* Should be aligned with other work to ensure likely completion in current release
* **[p2-medium][]**: Important work for later release.
* Should be done – eventually.
* **[p3-low][]**: Maybe, someday
* **[P0][]**: Drop everything and fix it.
* For dev channel: blocks the release. Valid cherry-pick.
* For release channel: worthy of a "dot" release
* **[P1][]**: Planned for the in-progress release
* Should be aligned with other work to ensure likely completion in current release
* **[P2][]**: Important work for later release.
* Should be done – eventually.
* **[P3][]**: Maybe, someday
* First candidates to close as "closed-not-planned"
* When we enter cherry pick season for release X...
* p0 issues: are the only fixes that will be taken for release X
* p1-3 issues:
* Milestone flag should be changed to release X+1 or
* p1 issues can be changed to p2/3 and milestone flag removed
* P0 issues: are the only fixes that will be taken for release X
* P1-3 issues:
* Milestone flag should be changed to release X+1 or
* P1 issues can be changed to p2/3 and milestone flag removed
## Using the `needs-info` label
@ -52,7 +46,7 @@ the issue after 14 days if the issue reporter does not respond.
## Follow up steps for Dart VM and Dart IO Library issues
Issues filed against the Dart VM (issues with label `area-vm` : [VM issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-vm+)) and IO library (issues with labels `area-library` `library-io` : [io library issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-library+label%3Alibrary-io)) are triaged at least weekly by a member of the Dart VM team.
Issues filed against the Dart VM (issues with label `area-vm` : [VM issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-vm+)) and IO library (issues with labels `area-core-library` `library-io` : [io library issues](https://github.com/dart-lang/sdk/issues?q=is%3Aissue+is%3Aopen+label%3Aarea-core-library+label%3Alibrary-io)) are triaged at least weekly by a member of the Dart VM team.
Triaging a bug entails the following steps
* Figure out if it is a bug, enhancement request, performance issue, general question, documentation issue or one of the other types and mark the issue appropriately as `type-bug`,`type-question`,`type-enhancement`,`type-performance` or one of the other types.
* If additional information is needed for addressing the bug please add the label `needs-info` to the issue and a comment back to the person filing the issue asking for information
@ -70,10 +64,9 @@ Triaging a bug entails the following steps
Issues may have their priorities adjusted up or down based on user feedback and milestones may also be adjusted based on available bandwidth in the team to address issues.
[SDK triage query]: https://goto.google.com/dart-triage
[move]: https://github.com/apps/move
[Dart SDK email tool]: https://dart-github-label-notifier.web.app
[p0-critical]: https://github.com/dart-lang/sdk/labels/p0-critical
[p1-high]: https://github.com/dart-lang/sdk/labels/p1-high
[p2-medium]: https://github.com/dart-lang/sdk/labels/p2-medium
[p3-low]: https://github.com/dart-lang/sdk/labels/p3-low
[P0]: https://github.com/dart-lang/sdk/labels/P0
[P1]: https://github.com/dart-lang/sdk/labels/P1
[P2]: https://github.com/dart-lang/sdk/labels/P2
[P3]: https://github.com/dart-lang/sdk/labels/P3
[no response]: https://github.com/dart-lang/sdk/blob/main/.github/workflows/no-response.yml