[libvirt] [PATCH v2 3/3] docs: Document the release notes process for contributors

[Andrea Bolognani]

On Thu, 2017-01-05 at 10:22 -0500, John Ferlan wrote:
> I would think this is simple enough to fix by adding a reference to the
> file you need to change...
> 
> Thus rather than :
> 
>   <p>Don't forget to update the <a href="news.html">release notes</a>
>      if your changes are significant.
> 
> perhaps use
> 
>   <p>Don't forget to update the <a href="news.html">release notes</a>
>      by changing <code>docs/news.xml</code> if your changes are
>      significant.
> 
> Or something like that to indicate what needs to be changed... Sure it
> could be obvious by reading news.html

That would work quite nicely indeed! Consider it squashed in.

> Of course if news.xml changes to news-v#.#.# as Daniel suggests, then
> you have a gift that keeps giving annually to update hacking.html.in to
> use the new version named file!

s/annualy/monthly/ ;)

-- 
Andrea Bolognani / Red Hat / Virtualization