2019-02-04 13:43:29 +01:00
|
|
|
> This file contains all changes that have not been released yet.
|
2019-07-05 10:05:02 +02:00
|
|
|
>
|
|
|
|
|
> Keep in mind the changelog is addressed to **users** and should be
|
|
|
|
|
> understandable by them.
|
2019-02-04 13:43:29 +01:00
|
|
|
|
|
|
|
|
### Enhancements
|
2022-10-19 18:43:48 +02:00
|
|
|
|
2022-10-07 11:23:32 +02:00
|
|
|
> Users must be able to say: “Nice enhancement, I'm eager to test it”
|
2022-10-19 18:43:48 +02:00
|
|
|
|
2022-11-30 11:18:33 +01:00
|
|
|
### Bug fixes
|
|
|
|
|
|
|
|
|
|
> Users must be able to say: “I had this issue, happy to know it's fixed”
|
|
|
|
|
|
2020-06-08 10:54:42 +02:00
|
|
|
### Packages to release
|
2019-02-04 13:43:29 +01:00
|
|
|
|
2022-05-24 11:01:05 +02:00
|
|
|
> When modifying a package, add it here with its release type.
|
2019-07-05 10:05:02 +02:00
|
|
|
>
|
2022-05-24 11:01:05 +02:00
|
|
|
> The format is the following: - `$packageName` `$releaseType`
|
2020-04-16 15:08:06 +02:00
|
|
|
>
|
2022-05-24 11:01:05 +02:00
|
|
|
> Where `$releaseType` is
|
2020-04-16 15:08:06 +02:00
|
|
|
>
|
|
|
|
|
> - patch: if the change is a bug fix or a simple code improvement
|
|
|
|
|
> - minor: if the change is a new feature
|
|
|
|
|
> - major: if the change breaks compatibility
|
2022-06-13 11:22:08 +02:00
|
|
|
>
|
|
|
|
|
> Keep this list alphabetically ordered to avoid merge conflicts
|
2022-05-04 09:57:21 +02:00
|
|
|
|
|
|
|
|
<!--packages-start-->
|
2022-12-06 10:42:51 +01:00
|
|
|
|
2022-05-04 09:57:21 +02:00
|
|
|
<!--packages-end-->
|
