Code

Changes between Initial Version and Version 1 of Ticket #13696, comment 13


Ignore:
Timestamp:
06/09/11 04:18:08 (3 years ago)
Author:
ramiro
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #13696, comment 13

    initial v1  
    44Thanks for the patch! But there is no need to close the ticket as ''fixed'', the ''has patch'' one is the way to mark it has a fix a fix ready for review. 
    55 
    6 ''Fixed'' is used when/if the issue is actually fixed either by applying it (or another fix) to the code (by a core committer) . Otherwise it will be completely under the radar for people looking for unsolved tickets or patches to review and commit, causing effectively the exact  contrary effect to the one you intended when you worked in the issue in the first time. 
     6''Fixed'' is used when/if the issue is actually fixed either by applying it (or another fix) to the code (by a core committer) . Otherwise it will be completely under the radar for people looking for unsolved tickets or patches to review and commit, causing effectively the exact  contrary effect to the one you intended when you worked in the issue in the first place. 
    77 
    88See https://docs.djangoproject.com/en/dev/internals/contributing/triaging-tickets/#closing-tickets