[libvirt] [libvirt PATCH v3] news: Update for 4.8.0 release

[Fabiano Fidêncio]

On Mon, 2018-10-01 at 15:22 +0200, Peter Krempa wrote:
> On Mon, Oct 01, 2018 at 15:04:37 +0200, Fabiano Fidêncio wrote:
> > Signed-off-by: Fabiano Fidêncio <fidencio at redhat.com>
> > ---
> > I went through the commits since last release and added a few notes
> > which seem to be relevant for the news.
> > 
> > In case you notice there's something missing, please, either send
> > me the
> > text to add it (and I'll re-sping this patch) and add the text
> > before
> > merging this one.
> > 
> > Changes since v1:
> > - Actually run make-check in order to be sure the changes are fine.
> > 
> > Changes since v2:
> > - Fixed and reworded some parts according to John's and Erik's
> >   suggestions.
> > - Added, according to Erik's suggestion:
> >   - util: Introduce VIR_AUTOCLOSE macro to automatically close
> > files' fds
> >   - virsh: Implement vsh-table in virsh and virsh-admin
> > ---
> >  docs/news.xml | 77
> > +++++++++++++++++++++++++++++++++++++++++++++++++++
> >  1 file changed, 77 insertions(+)
> > 
> > diff --git a/docs/news.xml b/docs/news.xml
> > index 3ed6ff8aeb..36692ba456 100644
> > --- a/docs/news.xml
> > +++ b/docs/news.xml
> > @@ -44,6 +44,18 @@
> >            and virDomainPMWakeup APIs.
> >          </description>
> >        </change>
> > +      <change>
> > +        <summary>
> > +          utils: Introduce monitor capability interface
> 
> Missing word 'resource'
> 
> > +        </summary>
> > +        <description>
> > +          The resource monitor has been introduced and it creates
> > the interface
> > +          for getting the host capability of the resource monitor
> > from the system
> > +          resource control.
> > +          The resource monitor takes the role of RDT monitoring
> > groups and could
> > +          be used to monitor the resource consumption information.
> 
> Not quite sure that this helps anybody in understanding the new
> feature.

May I ask for some help here to have it in a way that it would actually
help someone to understand the new feature?

> 
> > +        </description>
> > +      </change>
> >      </section>
> >      <section title="Removed features">
> >        <change>
> 
> [...]
> 
> > @@ -68,8 +89,64 @@
> >            Guest Agent.
> >          </description>
> >        </change>
> > +      <change>
> > +        <summary>
> > +          storage: Allow to use any format as input volume for
> > encryption
> > +        </summary>
> > +        <description>
> > +          Libvirt has supported 'raw' input volumes for encryption
> > since 4.5.0.
> > +          Now, it's not going to limit the usage to 'raw' only
> > anymore.
> > +        </description>
> > +      </change>
> > +      <change>
> > +        <summary>
> > +          libxl: Add support to set shadow memory for any guest
> > type
> > +        </summary>
> > +        <description>
> > +          PVH guests now can take advantage of using shadow
> > memory.
> 
> I'm not quite sure the users will know what this means.


And here as well?

> 
> > +        </description>
> > +      </change>
> > +      <change>
> > +        <summary>
> > +          util: Introduce VIR_AUTOCLOSE macro to automatically
> > close files' fds
> > +        </summary>
> > +        <description>
> > +          The Macro automatically force closes the fds by calling
> > +          <code>virForceCloseHelper</code> when the fd goes out of
> > scope and is
> > +          used to eliminate <code>VIR_FORCE_CLOSE</code> in
> > cleanup sections.
> > +        </description>
> 
> This is internal stuff not really worth mentioning in the news.

Okay, I'll drop this one.

> 
> > +      </change>