After the release it's necessary to add a new <release> section for the
upcomming release. Add a template so that it does not have to be
compiled over and over again.
---
 docs/news.xml | 21 +++++++++++++++++++++
 1 file changed, 21 insertions(+)

diff --git a/docs/news.xml b/docs/news.xml
index c2a2917c1..1ebe0eec3 100644
--- a/docs/news.xml
+++ b/docs/news.xml
@@ -20,6 +20,27 @@
      Lines should be kept under 80 columns, and should not exceed 100 columns.

      This file is validated against docs/news.rng schema.
+
+     Use the following template to add a new release section after the release:
+
+  <release version="FIXME" date="unreleased">
+    <section title="New features">
+      <change>
+        <summary/>
+      </change>
+    </section>
+    <section title="Improvements">
+      <change>
+        <summary/>
+      </change>
+    </section>
+    <section title="Bug fixes">
+      <change>
+        <summary/>
+      </change>
+    </section>
+  </release>
+
      -->

 <libvirt>
-- 
2.12.1

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list

On Tue, 2017-03-28 at 13:58 +0200, Peter Krempa wrote:
> After the release it's necessary to add a new <release> section for the
> upcomming release. Add a template so that it does not have to be

s/upcomming/upcoming/

[...]
> @@ -20,6 +20,27 @@
>       Lines should be kept under 80 columns, and should not exceed 100 columns.
> 
>       This file is validated against docs/news.rng schema.
> +
> +     Use the following template to add a new release section after the release:

s/ after the release//


ACK with these two nits fixed.

-- 
Andrea Bolognani / Red Hat / Virtualization

--
libvir-list mailing list
libvir-list@redhat.com
https://www.redhat.com/mailman/listinfo/libvir-list