diff options
| author | Preston Holmes <preston@ptone.com> | 2013-04-09 22:39:36 -0700 |
|---|---|---|
| committer | Preston Holmes <preston@ptone.com> | 2013-04-09 22:39:36 -0700 |
| commit | 18255779e9711354372085179d7bf94d803b6895 (patch) | |
| tree | 7ea38c41969059bdc9092c053da5c069a3cd2de5 /docs | |
| parent | 7441a29f52046c96c072e1ae1f21d0be488b5a76 (diff) | |
Added some further guidance to "accepted" triage stage
Now that DDN is gone, I felt it was worth some extra language
about what "accepted" means, and qualify what it means to be "safe"
to start writing a patch.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/internals/contributing/triaging-tickets.txt | 9 |
1 files changed, 8 insertions, 1 deletions
diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index 9c88d6961b..4ad0e8510d 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -119,7 +119,14 @@ Beyond that there are several considerations: * **Accepted + No Flags** The ticket is valid, but no one has submitted a patch for it yet. Often this - means you could safely start writing a patch for it. + means you could safely start writing a patch for it. This is generally more + true for the case of accepted bugs than accepted features. A ticket for a bug + that has been accepted means that the issue has been verified by at least one + triager as a legitimate bug - and should probably be fixed if possible. An + accepted new feature may only mean that one triager thought the feature would + be good to have, but this alone does not represent a consensus view or imply + with any certainty that a patch will be accepted for that feature. Seek more + feedback before writing an extensive patch if you are in doubt. * **Accepted + Has Patch** |