Changes between Version 26 and Version 27 of NewCommittersGuide

Timestamp:

Oct 6, 2013, 5:59:55 PM (11 years ago)

Author:

mkae (Marko Käning)

Comment:

Move details concerning commit messages into CommitRules

NewCommittersGuide

@@ -18 +18 @@
  1. Run `port lint` before committing to be sure not to violate one of the guidelines
  1. Commit messages should make clear what has been changed (see CommitRules)
-  1. Mention the names of the affected ports (or state what they have in common if there are too many to list individually), since this information is not visible in the revision log
-  1. Be specific about what changes were made (for example, when updating to a new upstream version, mention the version number) and, if it's not completely obvious, why they were made
-  1. Reference any tickets that are related to the change, preferably with a [wiki:TracLinks Trac link]
  1. Under most circumstances, do not modify a port belonging to another maintainer; this is to be done either via a Trac ticket or by direct communication with the maintainer.  Exceptions are:
    1. When a port is broken (and the update should be just to fix the port, no other updates "while you're there")