xen-orchestra/CHANGELOG.unreleased.md

> This file contains all changes that have not been released yet.
>
> Keep in mind the changelog is addressed to **users** and should be
> understandable by them.

### Enhancements

> Users must be able to say: “Nice enhancement, I'm eager to test it”

### Bug fixes

> Users must be able to say: “I had this issue, happy to know it's fixed”

### Packages to release

> Packages will be released in the order they are here, therefore, they should
> be listed by inverse order of dependency.
>
> Rule of thumb: add packages on top.
>
> The format is the following: - `$packageName` `$version`
>
> Where `$version` is
>
> - 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
>
> In case of conflict, the highest (lowest in previous list) `$version` wins.
chore(CHANGELOG.unreleased): contains unreleased changes Inspired by [Prettier](https://github.com/prettier/prettier/blob/master/CHANGELOG.unreleased.md). Changes should go there instead of CHANGELOG, they will be moved during the release process. This change should prevent the issue where old updated PRs added changes at incorrect positions in the CHANGELOG. 2019-02-04 13:43:29 +01:00			`> This file contains all changes that have not been released yet.`
feat(CHANGELOG.unreleased): add instructions for devs (#4333) 2019-07-05 10:05:02 +02:00			`>`
			`> Keep in mind the changelog is addressed to users and should be`
			`> understandable by them.`
chore(CHANGELOG.unreleased): contains unreleased changes Inspired by [Prettier](https://github.com/prettier/prettier/blob/master/CHANGELOG.unreleased.md). Changes should go there instead of CHANGELOG, they will be moved during the release process. This change should prevent the issue where old updated PRs added changes at incorrect positions in the CHANGELOG. 2019-02-04 13:43:29 +01:00
			`### Enhancements`

fix(CHANGELOG{,.unreleased}): move backup dev notes Introduced by e7b846155 2021-04-13 10:26:26 +02:00			`> Users must be able to say: “Nice enhancement, I'm eager to test it”`

chore(CHANGELOG.unreleased): contains unreleased changes Inspired by [Prettier](https://github.com/prettier/prettier/blob/master/CHANGELOG.unreleased.md). Changes should go there instead of CHANGELOG, they will be moved during the release process. This change should prevent the issue where old updated PRs added changes at incorrect positions in the CHANGELOG. 2019-02-04 13:43:29 +01:00			`### Bug fixes`

fix(CHANGELOG{,.unreleased}): move backup dev notes Introduced by e7b846155 2021-04-13 10:26:26 +02:00			`> Users must be able to say: “I had this issue, happy to know it's fixed”`

chore(CHANGELOG.unreleased): clarify that packages are not yet released 2020-06-08 10:54:42 +02:00			`### Packages to release`
chore(CHANGELOG.unreleased): contains unreleased changes Inspired by [Prettier](https://github.com/prettier/prettier/blob/master/CHANGELOG.unreleased.md). Changes should go there instead of CHANGELOG, they will be moved during the release process. This change should prevent the issue where old updated PRs added changes at incorrect positions in the CHANGELOG. 2019-02-04 13:43:29 +01:00
feat(CHANGELOG.unreleased): add instructions for devs (#4333) 2019-07-05 10:05:02 +02:00			`> Packages will be released in the order they are here, therefore, they should`
			`> be listed by inverse order of dependency.`
			`>`
			`> Rule of thumb: add packages on top.`
chore(CHANGELOG.unreleased): doc for package version 2020-04-16 15:08:06 +02:00			`>`
fix(CHANGELOG.unreleased): better syntax for variables 2020-04-16 15:09:11 +02:00			> The format is the following: - `$packageName` `$version`
chore(CHANGELOG.unreleased): doc for package version 2020-04-16 15:08:06 +02:00			`>`
fix(CHANGELOG.unreleased): better syntax for variables 2020-04-16 15:09:11 +02:00			> Where `$version` is
chore(CHANGELOG.unreleased): doc for package version 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`
			`>`
fix(CHANGELOG.unreleased): better syntax for variables 2020-04-16 15:09:11 +02:00			> In case of conflict, the highest (lowest in previous list) `$version` wins.