[libvirt] [PATCH for 5.1.0] news: Update for 5.1.0 release

Ján Tomko jtomko at redhat.com
Thu Feb 28 13:11:22 UTC 2019


On Thu, Feb 28, 2019 at 11:43:56AM +0100, Michal Privoznik wrote:
>Not exhaustive list of new features, improvements and bugfixes.
>
>Signed-off-by: Michal Privoznik <mprivozn at redhat.com>
>---
> docs/news.xml | 201 ++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 201 insertions(+)
>
>diff --git a/docs/news.xml b/docs/news.xml
>index 9c5ae7e8a3..813f1a93e3 100644
>--- a/docs/news.xml
>+++ b/docs/news.xml
>@@ -69,8 +69,104 @@
>+      <change>
>+        <summary>
>+          Support for newer wireshark
>+        </summary>
>+        <description>
>+          Wireshark supports out of tree builds of dissectors since its
>+          2.5.0 release. Adapt libvirt to that. This affects minimal
>+          required version then too.
>+        </description>
>+      </change>
>+      <change>
>+        <summary>
>+          More use of VIR_AUTOFREE() and friends
>+        </summary>
>+        <description>
>+          Usuaully, this would be viewed as an internal change that
>+          should not concern users.

Usuaully, justification for including a change goes in the commit
message. ;)

>However, since libvirt is written in
>+          memory unsafe language some memory leaks might have been
>+          actually fixed by using VIR_AUTOFREE(). It is definitely step
>+          towards defensive programming.

I thought I was programming reasonably defensively already.
Anyway I also vote against including this in the news.

>+        </description>
>+      </change>
>     </section>
>     <section title="Bug fixes">
>       <change>
>@@ -133,6 +229,111 @@
>           attribute of the network bridge element).
>         </description>
>       </change>
>+      <change>
>+        <summary>
>+          Refresh block jobs on daemon restart
>+        </summary>
>+        <description>
>+          In case the daemon is restarted it now fetches new state of
>+          blockjobs. This means that libvirt does not lose track of
>+          block jobs anymore.
>+        </description>
>+      </change>

This change is only relevant for blockdev which is not enabled yet.
For "legacy" blockjobs we get the state from QEMU. So this change can
be dropped.

Jano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20190228/f587c918/attachment-0001.sig>


More information about the libvir-list mailing list