Changes between Version 21 and Version 22 of NewCommittersGuide
- Timestamp:
- Apr 1, 2010, 2:46:02 PM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
NewCommittersGuide
v21 v22 5 5 == Port Committer Responsibilities == 6 6 7 1. PortIndex is now updated automatically (every hour) so it must not be touched 8 1. A commit affects one port (including however many files are required for that one port) 9 1. The exception to the one port/one commit rule is where several Portfiles make use of some feature which is in need of updating 10 1. Due to a new feature which has been added to the current release to fix hacks used by various Portfiles 11 1. A command is found to be broken 12 1. You need to change your email address for your ports 7 1. Do not touch PortIndex. It is updated automatically every hour 8 1. A commit affects one port 9 1. An exception to 2. would be several Portfiles making use of some feature which requires an update 10 1. A new feature has been released which obsoletes previous hacks 11 1. A command or option is found to be broken 12 1. Combined updates for similar ports (py25-* and py26-*) 13 1. Changing maintainer email address for your ports 13 14 1. Other, similar reasons 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 difficult15 1. Make whitespace changes in a separate commit. To keep diffs readable for review whitespace changes should be done in a separate commit without any functional changes. 15 16 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) 16 17 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)