Changes between Version 19 and Version 20 of NewCommittersGuide
- Timestamp:
- Jul 28, 2009, 3:36:46 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewCommittersGuide
v19 v20 13 13 1. Other, similar reasons 14 14 1. When changing the whitespace of a Portfile, do so in a separate commit (without any functional changes) as otherwise the commingling of functional and whitespace changes makes reviewing diffs difficult 15 1. All committers must subscribe to the [http://lists.macosforge.org/mailman/listinfo/macports-changes macports-changes] list under their MacPorts credentials to keep track of current changes and because the list is subscriber-post-only, so commit messages will otherwise be rejected16 15 1. New top-level categories (those which are represented by subdirectories directly beneath dports/) need to be approved prior to adding; secondary categories (the second and later ones listed on the '''categories''' Portfile key) can be added when it makes sense (since these really only show under the web interface, and do not necessarily have a filesystem representation) 17 16 1. Make sure the port name matches between the MacPorts svn directory name and the '''name''' Portfile key (while the system works fine when they don't, keeping them synchronized avoids confusing situations)