|
| 1 | +# CHANGELOG |
| 2 | + |
| 3 | +This directory contains "news fragments", |
| 4 | +i.e. short files that contain a small markdown-formatted bit of text |
| 5 | +that will be added to the CHANGELOG when it is next compiled. |
| 6 | + |
| 7 | +The CHANGELOG will be read by users, |
| 8 | +so this description should be aimed to mkdocstrings-python-accessors users |
| 9 | +instead of describing internal changes which are only relevant to developers. |
| 10 | +Merge requests in combination with our git history |
| 11 | +provide additional developer-centric information. |
| 12 | + |
| 13 | +Make sure to use phrases in the past tense and use punctuation, examples: |
| 14 | + |
| 15 | +``` |
| 16 | +Improved verbose diff output with sequences. |
| 17 | +
|
| 18 | +Terminal summary statistics now use multiple colors. |
| 19 | +``` |
| 20 | + |
| 21 | +Each file should have a name of the form `<MR>.<TYPE>.md`, where `<MR>` is the merge request number, and `<TYPE>` is one of: |
| 22 | + |
| 23 | +* `feature`: new user facing features, like new command-line options and new behaviour. |
| 24 | +* `improvement`: improvement of existing functionality, usually without requiring user intervention |
| 25 | +* `fix`: fixes a bug. |
| 26 | +* `docs`: documentation improvement, like rewording an entire section or adding missing docs. |
| 27 | +* `deprecation`: feature deprecation. |
| 28 | +* `breaking`: a change which may break existing uses, such as feature removal or behaviour change. |
| 29 | +* `trivial`: fixing a small typo or internal change that might be noteworthy. |
| 30 | + |
| 31 | +So for example: `123.feature.md`, `456.fix.md`. |
| 32 | + |
| 33 | +Since you need the merge request number for the filename, you must submit a MR first. |
| 34 | +From this MR, you can get the MR number and then create the news file. |
| 35 | +A single MR can also have multiple news items, |
| 36 | +for example a given MR may add a feature as well as deprecate some existing functionality. |
| 37 | + |
| 38 | +If you are not sure what issue type to use, don't hesitate to ask in your MR. |
| 39 | + |
| 40 | +`towncrier` preserves multiple paragraphs and formatting |
| 41 | +(code blocks, lists, and so on), |
| 42 | +but for entries other than features it is usually better to stick to a single paragraph to keep it concise. |
| 43 | +You may also use [mkdocs-autorefs cross-referencing](https://mkdocstrings.github.io/autorefs/) |
| 44 | +within your news items to link to other documentation. |
| 45 | + |
| 46 | +You can also run `towncrier build --draft --version draft` |
| 47 | +to see the draft changelog that will be appended to the CHANGELOG on the next release. |
0 commit comments