diff options
| author | Cody Scott <cody.j.b.scott@gmail.com> | 2013-11-21 18:46:35 -0500 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2013-11-22 09:07:10 -0500 |
| commit | 4a54b69e8829fd3e7994f5248c4711c4f594e8a5 (patch) | |
| tree | 56159463b021988642874f6474bfa9a30221f8f5 /docs | |
| parent | 9c6b57f709bb6123d8abae6ba05e92085ec2f426 (diff) | |
Fixed sentence structure in docs/internals/contributing/triaging-tickets.txt
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/internals/contributing/triaging-tickets.txt | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/internals/contributing/triaging-tickets.txt b/docs/internals/contributing/triaging-tickets.txt index ea0e6d9030..92f9406c5b 100644 --- a/docs/internals/contributing/triaging-tickets.txt +++ b/docs/internals/contributing/triaging-tickets.txt @@ -372,16 +372,16 @@ Then, you can help out by: any activity in a long time, it's possible that the problem has been fixed but the ticket hasn't yet been closed. -* Identifying trends and themes in the tickets. If there a lot of bug +* Identifying trends and themes in the tickets. If there are a lot of bug reports about a particular part of Django, it may indicate we should consider refactoring that part of the code. If a trend is emerging, you should raise it for discussion (referencing the relevant tickets) on |django-developers|. -* Verify if patches submitted by other users are correct. If they do and - also contain appropriate documentation and tests then move them to the - "Ready for Checkin" stage. If they don't then leave a comment to explain - why and set the corresponding flags ("Patch needs improvement", +* Verify if patches submitted by other users are correct. If they are correct + and also contain appropriate documentation and tests then move them to the + "Ready for Checkin" stage. If they are not correct then leave a comment to + explain why and set the corresponding flags ("Patch needs improvement", "Needs tests" etc.). .. note:: |