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”

- [VM/Network] Show IP addresses in front of their VIFs [#4882](https://github.com/vatesfr/xen-orchestra/issues/4882) (PR [#5003](https://github.com/vatesfr/xen-orchestra/pull/5003))

### Bug fixes

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

- [VM/Creation] Fix `insufficient space` which could happened when moving and resizing disks (PR [#5044](https://github.com/vatesfr/xen-orchestra/pull/5044))
- [VM/General] Fix displayed IPV6 instead of IPV4 in case of an old version of XenServer (PR [#5036](https://github.com/vatesfr/xen-orchestra/pull/5036)))

### Released packages

> 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.

- xo-server patch
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`

feat(CHANGELOG.unreleased): add instructions for devs (#4333) 2019-07-05 10:05:02 +02:00			`> Users must be able to say: “Nice enhancement, I'm eager to test it”`

feat(xo-web/vm/network): show IPs in front of their VIFs (#5003) Fixes #4882 2020-06-02 09:26:31 +02:00			`- [VM/Network] Show IP addresses in front of their VIFs [#4882](https://github.com/vatesfr/xen-orchestra/issues/4882) (PR [#5003](https://github.com/vatesfr/xen-orchestra/pull/5003))`

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`

feat(CHANGELOG.unreleased): add instructions for devs (#4333) 2019-07-05 10:05:02 +02:00			`> Users must be able to say: “I had this issue, happy to know it's fixed”`
fix(xo-server/host.isHostServerTimeConsistent): dont return false on check failure (#4540) 2019-09-24 10:46:43 +02:00
fix(xo-server#createVm): move VDIs before resize them (#5044) See xoa-support#2535 Otherwise resizing might file due to space limitation on the template VDI's SR. 2020-06-05 13:37:18 +02:00			- [VM/Creation] Fix `insufficient space` which could happened when moving and resizing disks (PR [#5044](https://github.com/vatesfr/xen-orchestra/pull/5044))
fix(xo-server#_extractIpFromVmNetworks): support old ipv4 protocol (#5036) See xoa-support#2540 In case of an old version of guest tools, the VM ipv4 isn't reported. This issue is due to a non-existant `n/ipv4/m` property in the VM addresses which is a new protocol. 2020-06-08 09:52:33 +02:00			`- [VM/General] Fix displayed IPV6 instead of IPV4 in case of an old version of XenServer (PR [#5036](https://github.com/vatesfr/xen-orchestra/pull/5036)))`
fix(xo-server#createVm): move VDIs before resize them (#5044) See xoa-support#2535 Otherwise resizing might file due to space limitation on the template VDI's SR. 2020-06-05 13:37:18 +02:00
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			`### Released packages`

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.
fix(xo-server#createVm): move VDIs before resize them (#5044) See xoa-support#2535 Otherwise resizing might file due to space limitation on the template VDI's SR. 2020-06-05 13:37:18 +02:00
			`- xo-server patch`