Download Reference Manual
The Developer's Library for D
About Wiki Forums Source Search Contact

Changes between Version 5 and Version 6 of CodeMaintenanceGuide

Show
Ignore:
Author:
yidabu (IP: 60.187.167.249)
Timestamp:
09/19/07 01:50:31 (7 years ago)
Comment:

Mantainer to Maintainer

Legend:

Unmodified
Added
Removed
Modified
  • CodeMaintenanceGuide

    v5 v6  
    2121=== Terms === 
    2222 
    23  * '''Mantainer''' : Original author of code, or person later assigned maintainership of a given portion of code. 
     23 * '''Maintainer''' : Original author of code, or person later assigned maintainership of a given portion of code. 
    2424 * '''Project lead''' : This is at any given time, the current administrative and technical leading group of Tango. Currently it consists of Kris Bell(principal developer of Mango), Sean Kelly (principal developer of Ares), Lars Ivar Igesund (administrative resource). 
    25  * '''Contributor''' : This a person that at some point have contributed to Tango, either through testing, writing of documentation, code patches or mantainership. 
     25 * '''Contributor''' : This a person that at some point have contributed to Tango, either through testing, writing of documentation, code patches or Maintainership. 
    2626 * '''Community''' : This is the group of contributors and/or people at any time using Tango. 
    2727 * '''Private branch''' : A private branch in the repository where a developer can test and develop new features. 
    3535 * All commits of any significance are to be accompanied by a commit message saying what was fixed or added, and include the relevant ticket number if applicable. This to facilitate the usage of the svn log for change logs for new releases. 
    3636 * Very obvious bugfixes (single line fixes) and compile fixes, may usually be committed by anyone with commit privileges. This also apply to simple documentation fixes. 
    37  * Semantic changes to a module's code, for instance change in behaviour, or addition of new functionality, should only be committed by that module's ''mantainer'', and will thus need to be accepted by that person. If it also will affect other parts of the repository, it will first need to be discussed with the ''project lead'' which again should choose to ask the community if the matter is considered to be large and/or controversial. 
    38  * If semantic code changes are proposed to the mantainer, but the nature of the change is thus that it cannot be immediately rejected or accepted, a patch need to be created. This should be committed to the ''patches/proposals/'' directory of trunk or the given branch, whichever applies. A ticket describing the issue or proposal that the patch fix should be created (unless it already exists), and the patch should be referenced in the ticket. The acceptation process for the patch, will otherwise follow the same process as for semantic changes. 
     37 * Semantic changes to a module's code, for instance change in behaviour, or addition of new functionality, should only be committed by that module's ''Maintainer'', and will thus need to be accepted by that person. If it also will affect other parts of the repository, it will first need to be discussed with the ''project lead'' which again should choose to ask the community if the matter is considered to be large and/or controversial. 
     38 * If semantic code changes are proposed to the Maintainer, but the nature of the change is thus that it cannot be immediately rejected or accepted, a patch need to be created. This should be committed to the ''patches/proposals/'' directory of trunk or the given branch, whichever applies. A ticket describing the issue or proposal that the patch fix should be created (unless it already exists), and the patch should be referenced in the ticket. The acceptation process for the patch, will otherwise follow the same process as for semantic changes. 
    3939   * Accepted patches will after they are applied, be put into ''patches/proposals/accepted/''. 
    4040   * Rejected patches will be put into ''patches/proposals/rejected/''.