Changeset 31669 for trunk/base/HACKING

Dec 2, 2007, 6:09:13 PM (13 years ago)

Include hacking rules for commits to base with respect to the ChangeLog file

NOTE: Needless to say, I'm more than open to suggestions to improve the fluency of this policy.

1 edited


  • trunk/base/HACKING

    r30982 r31669  
    1 Project naming and copyright attribution:
     1# Project naming and copyright attribution:
    33* "The MacPorts Project" is the string that shall be used whereever there's a need to reference our project name, such as in copyright notices.
    12 Whitespace rules as discussed on the development list (macports-dev):
     12# Commits to the "base" component of the repository:
     14* Any commit made to the "base" component of the repository should be accompanied by a corresponding entry in the base/ChanegeLog file, full with information
     15    of the svn revision information of the commit and Trac ticket number the commit references and/or fixes, if any.
     16* Such entries to the ChangeLog need not be full duplications of their related commit logs if the latter are thorough explanations of what's involved in the commit.
     17    In such cases it's perfectly acceptable to enter just a summary of the commit and point the reader to further information through the related svn revision
     18    and Trac ticket number (if applicable).
     19* Related commits to "base" may be grouped in a single ChangeLog entry, provided the full list of svn revisions and Trac ticket numbers referenced (if applicable)
     20    is included.
     21* Commits to "base" need not update the base/NEWS file, as such will be constructed with the relevant information at MacPorts release time by the release engineers.
     24# Whitespace rules as discussed on the development list (macports-dev):
    1426* All source code files MUST use soft tabs at a tabstop of 4. No hard tabs are allowed.
Note: See TracChangeset for help on using the changeset viewer.