Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse code

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.
  • Loading branch information...
commit 18255779e9711354372085179d7bf94d803b6895 1 parent 7441a29
Preston Holmes authored April 09, 2013
9  docs/internals/contributing/triaging-tickets.txt
@@ -119,7 +119,14 @@ Beyond that there are several considerations:
119 119
 * **Accepted + No Flags**
120 120
 
121 121
   The ticket is valid, but no one has submitted a patch for it yet. Often this
122  
-  means you could safely start writing a patch for it.
  122
+  means you could safely start writing a patch for it. This is generally more
  123
+  true for the case of accepted bugs than accepted features. A ticket for a bug
  124
+  that has been accepted means that the issue has been verified by at least one
  125
+  triager as a legitimate bug - and should probably be fixed if possible. An
  126
+  accepted new feature may only mean that one triager thought the feature would
  127
+  be good to have, but this alone does not represent a consensus view or imply
  128
+  with any certainty that a patch will be accepted for that feature. Seek more
  129
+  feedback before writing an extensive patch if you are in doubt.
123 130
 
124 131
 * **Accepted + Has Patch**
125 132
 

0 notes on commit 1825577

Please sign in to comment.
Something went wrong with that request. Please try again.