Changes between Version 2 and Version 3 of DevelopersGuide/PatchGuide


Ignore:
Timestamp:
2013-03-26T18:39:49+01:00 (12 years ago)
Author:
stoecker
Comment:

Add comment about large changes

Legend:

Unmodified
Added
Removed
Modified

  • DevelopersGuide/PatchGuide

    v2 v3  
    1212* Keep the patch as readable as possible: Do not correct the formatting / indentation of any code that need not be changed. Do not unnecessarily reorder methods, etc. (Improvements of the documentation are always welcome, though.)
    1313* If you have multiple related changes, it is usually better to combine them all in one big patch, rather than attaching a long list of diffs. However, sometimes it may be useful to split the more controversial parts of the changes from those that can be applied without discussion.
     14* Large changes should be splitted:
     15   * first required infrastructure changes in smaller parts
     16   * final work later (should be small as well, after infrastructe fixes are applied)
    1417
    1518Please be patient—there can be various reasons, why your patch is not dealt with. If you don't get any reaction for two weeks, it may be a good idea to bring the topic up again and ask for a status update.