Code

Changes between Version 6 and Version 7 of ContributingHowTo


Ignore:
Timestamp:
10/05/10 17:07:46 (4 years ago)
Author:
PaulM
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ContributingHowTo

    v6 v7  
    3535 * '''Accepted''': The big grey area! The absolute meaning of "accepted" is that the issue described in the ticket is valid and is in some stage of being worked on. Beyond that there are several considerations: 
    3636   * '''Accepted + No Flags''': The ticket is valid, but no one has submitted a patch for yet. Often this means you could safely start writing a patch for it. 
    37    * '''Accepted + Has Patch''': The ticket is waiting for people to review the supplied patch. This means downloading the patch and trying it out, verifying that it contains tests and docs, and leaving feedback on the ticket. 
     37   * '''Accepted + Has Patch''': The ticket is waiting for people to review the supplied patch. This means downloading the patch and trying it out, verifying that it contains tests and docs, running the test suite with the included patch, and leaving feedback on the ticket. 
    3838   * '''Accepted + Has Patch + (any other flag)''': This means the ticket has been reviewed, and has been found to need further work. "Needs tests" and "Needs documentation" are self-explanatory. "Patch needs improvement" will generally be accompanied by a comment on the ticket explaining what is needed to improve the code. 
    3939 
     
    7575 
    7676 3. My ticket has been in DDN forever! What should I do? 
    77    * Design Decision Needed requires consensus about the right solution. At the very least it needs consensus among the core developers, and ideally it has consensus from the community as well. The best way to accomplish this is to start a thread on the Django Developers mailing list, or for very complex issues to start a wiki page summarizing the problem and the possible solutions. 
     77   * Design Decision Needed requires consensus about the right solution. At the very least it needs consensus among the core developers, and ideally it has consensus from the community as well. The best way to accomplish this is to start a thread on the Django Developers mailing list, and for very complex issues to start a wiki page summarizing the problem and the possible solutions. 
    7878 
    7979 4. My ticket has been in RFC forever! What should I do?