... | ... | @@ -82,6 +82,8 @@ If you really like to, you can squash your own commits. Nobody in the Kea team d |
|
|
|
|
|
Changelog entries are requires for every change that is visible by a user. This covers things like new features (they may want to start using it), bug fixes (they may be affected and a fix may be the reason to upgrade), changes to build process (they may need to install new software dependency or, even when the dependency installation is automated, they should be aware that new piece of software will appear in their system) or documentation. Changelog should be modified on a branch and then merged to master. This is the same change as everything else, and should go through the usual review process.
|
|
|
|
|
|
The Changelog entries will be used as part of the release notes. Please make sure the text is descriptive and understandable by users, who may not be experts or don't follow developers' discussions.
|
|
|
|
|
|
An example changelog entry looks like this:
|
|
|
|
|
|
```
|
... | ... | |