Documentation update and questions

Marco Krohn marco.krohn at googlemail.com
Wed Feb 23 00:44:14 CET 2011


Dear all,

I did a few smaller changes to the documentation of the Commit Digest
on the community wiki (btw thanks for adding the draft letter Roger!).

For the classification guidelines  (
http://community.kde.org/Commit_Digest/Guidelines ) I propose to
change


"Bug Fixes: this category contains all commits which mention a bug
number in the message. It also contains commits which fix something
according to the comment but do not have a bug report attached (these
commits need to be important though, remember the 5% rule!)."


to


"Bug Fixes: this category contains all commits which mention a bug
number in the message (if the bug refers to a bug and is not a
wishlist item (*)). It also contains commits which fix something
according to the comment but do not have a bug report attached (these
commits need to be important though, remember the 5% rule!).

Features: comprises all commits that either mention a bug number
(which refers to a wishlist item (*)) or any commits which are about
the addition of a interesting or important feature."

(*) this can be done by looking at the bugs severity in the summary
box: "normal", "major", "critical" refers to a bug (e.g.,
http://bugs.kde.org/show_bug.cgi?id=266727 ), while "wishlist" refers
to a feature (e.g., http://bugs.kde.org/show_bug.cgi?id=256651 ). If
the severity is "minor" or "trivial" (
http://bugs.kde.org/page.cgi?id=fields.html#bug_severity ) it is in
general not recommended to include the respective commit.


Please let me know if you have any additions etc.

Thanks and have a nice evening,
  Marco


P.S. Also it would be helpful (also for me) if someone could add the
most important steps for creating a new Commit-Digest (
http://community.kde.org/Commit_Digest/Editor_guidelines ).


More information about the Digest mailing list