From f7f2ade4b22244ad0451da904bf7c9e2c9415358 Mon Sep 17 00:00:00 2001 From: Florian Forster Date: Thu, 7 Feb 2019 08:55:21 +0100 Subject: [PATCH] CONTRIBUTING.md: Improve wording around ChangeLog; fix example. --- CONTRIBUTING.md | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e4d683c9..68c338e8 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -53,18 +53,18 @@ the mailing list have a tendency to fall through the cracks. ### ChangeLog -All PRs need to have a one-line description in the initial pull request body. +All PRs need to have a one-line summary in the initial pull description. This information is used to automatically generate release notes. Follow this style: ``` -Foo plugin: A specific issue people had has been fixed. +ChangeLog: Foo plugin: A specific issue people had has been fixed. ``` -Start with "Foo plugin" to give the reader context for the information. Other -common prefixes are "collectd" for the core daemon and "Build system". Use past -tense and passive voice the for remainder, e.g. "a bug has been fixed", "a -feature has been added". +The summary should start with "Foo plugin" to give the reader context for the +information. Other common prefixes are "collectd" for the core daemon and +"Build system". Use past tense and passive voice the for remainder, e.g. "a bug +has been fixed", "a feature has been added". Some PRs should not be added to the release notes, e.g. changes to project internal documentation (such as this file). Those changes are not interesting -- 2.11.0