Gilles Peskine | b695d5e | 2020-03-27 20:06:12 +0100 | [diff] [blame^] | 1 | # Pending changelog entry directory |
| 2 | |
Gilles Peskine | 7c3f7cd | 2020-03-27 19:47:35 +0100 | [diff] [blame] | 3 | This directory contains changelog entries that have not yet been merged |
| 4 | to the changelog file ([`../ChangeLog`](../ChangeLog)). |
| 5 | |
Gilles Peskine | b695d5e | 2020-03-27 20:06:12 +0100 | [diff] [blame^] | 6 | ## Changelog entry file format |
| 7 | |
Gilles Peskine | 7c3f7cd | 2020-03-27 19:47:35 +0100 | [diff] [blame] | 8 | A changelog entry file must have the extension `*.txt` and must have the |
| 9 | following format: |
| 10 | |
| 11 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 12 | Security |
| 13 | * Change description. |
| 14 | * Another change description. |
| 15 | |
| 16 | Features |
Gilles Peskine | b695d5e | 2020-03-27 20:06:12 +0100 | [diff] [blame^] | 17 | * Yet another change description. This is a long change description that |
| 18 | spans multiple lines. |
Gilles Peskine | 7c3f7cd | 2020-03-27 19:47:35 +0100 | [diff] [blame] | 19 | * Yet again another change description. |
| 20 | |
| 21 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 22 | |
Gilles Peskine | b695d5e | 2020-03-27 20:06:12 +0100 | [diff] [blame^] | 23 | The permitted changelog entry categories are as follows: |
| 24 | <!-- Keep this synchronized with STANDARD_CATEGORIES in assemble_changelog.py! --> |
| 25 | |
| 26 | API changes |
| 27 | Default behavior changes |
| 28 | Requirement changes |
| 29 | New deprecations |
| 30 | Removals |
| 31 | Features |
| 32 | Security |
| 33 | Bugfix |
| 34 | Changes |
| 35 | |
| 36 | Use “Changes” for anything that doesn't fit in the other categories, such as |
| 37 | performance, documentation and test improvements. |
| 38 | |
| 39 | ## How to write a changelog entry |
| 40 | |
| 41 | Each entry starts with three spaces, an asterisk and a space. Continuation |
| 42 | lines start with 5 spaces. Lines wrap at 79 characters. |
| 43 | |
| 44 | Write full English sentences with proper capitalization and punctuation. Use |
| 45 | the present tense. Use the imperative where applicable. For example: “Fix a |
| 46 | bug in mbedtls_xxx() ….” |
| 47 | |
| 48 | Include GitHub issue numbers where relevant. Use the format “#1234” for an |
| 49 | Mbed TLS issue. Add other external references such as CVE numbers where |
| 50 | applicable. |
| 51 | |
| 52 | Credit the author of the contribution if the contribution is not a member of |
| 53 | the Mbed TLS development team. Also credit bug reporters where applicable. |
| 54 | |
| 55 | **Explain why, not how**. Remember that the audience is the users of the |
| 56 | library, not its developers. In particular, for a bug fix, explain the |
| 57 | consequences of the bug, not how the bug was fixed. For a new feature, explain |
| 58 | why one might be interested in the feature. For an API change or a deprecation, |
| 59 | explain how to update existing applications. |
| 60 | |
| 61 | See [existing entries](../ChangeLog) for examples. |
| 62 | |
| 63 | ## How `ChangeLog` is updated |
| 64 | |
| 65 | Run [`../scripts/assemble_changelog.py`](../scripts/assemble_changelog.py) |
| 66 | from a Git working copy |
| 67 | to move the entries from files in `ChangeLog.d` to the main `ChangeLog` file. |