iSharkFly-Docs
/
angular-docs-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

chore: update TRIAGE_AND_LABELS.md

This commit is contained in:
Miško Hevery 2015-06-05 11:20:05 -07:00
parent dc6e7eb19b
commit 13d0815839
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
TRIAGE_AND_LABELS.md
View File

@ -9,7 +9,7 @@ Every triaged issue must have four attributes assigned to it:
* `priority` -- P0 through P4. P0 issues are "drop everything and do this now". P4 are nice to have.
* `component` -- Which area of Angular knowledge this relates to.
* `effort` -- Rough assessment of how much work this issue is. E.g. `effort: hour` means
* `effort` -- Rough assessment of how much work this issue is. E.g. `effort: easy` means
"probably a few hours of work".
* `type` -- Whether this issue is a bug, feature, or other kind of task.
@ -127,7 +127,8 @@ to work on next.
* `comp: core/directives` -- directives
* `comp: core/forms` -- forms → *vsavkin*
* `comp: core/pipes` -- pipes
* `comp: core/templating` -- templating
* `comp: core/view` -- runtime processing of the `View`s
* `comp: core/view/compiler` -- static analysis of the templates which generate `ProtoView`s.
* `comp: core/testbed` -- e2e tests and support for them
* `comp: dart-transformer` -- Dart transforms → *kegluneq*, *jakemac*
* `comp: data-access` -- → *jeffbcross*
@ -163,4 +164,4 @@ This is an issue causing user pain for early adopter customers `cust: GT` or `cu
### WORKS_AS_INTENDED
Only used on closed issues, to indicate to the reporter why we closed it.
Only used on closed issues, to indicate to the reporter why we closed it.