[libvirt] [PATCH] NEWS: Start using the improved format
This entry is meant to both get the ball rolling on the switch and to provide a blueprint of what NEWS file entries are supposed to look like. --- We need to start somewhere, and what better way than talking about the change itself? ;) docs/news.html.in | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/news.html.in b/docs/news.html.in index deeee4d..fca1e29 100644 --- a/docs/news.html.in +++ b/docs/news.html.in @@ -16,6 +16,15 @@ to gauge progress. </p> + <h3>v2.5.0: <i>unreleased</i></h3> + <ul> + <li>Switch to an improved NEWS file format<br/> + List user-visible changes instead of single commits for a better + high-level overview of differences between libvirt releases + </li> + <li>Various bug fixes and improvements</li> + </ul> + <h3>v2.4.0: Nov 1 2016</h3> <ul> <li>Documentation:<br/> -- 2.7.4
On Fri, Nov 18, 2016 at 05:16:47PM +0100, Andrea Bolognani wrote:
This entry is meant to both get the ball rolling on the switch and to provide a blueprint of what NEWS file entries are supposed to look like. --- We need to start somewhere, and what better way than talking about the change itself? ;)
docs/news.html.in | 9 +++++++++ 1 file changed, 9 insertions(+)
diff --git a/docs/news.html.in b/docs/news.html.in index deeee4d..fca1e29 100644 --- a/docs/news.html.in +++ b/docs/news.html.in @@ -16,6 +16,15 @@ to gauge progress. </p>
+ <h3>v2.5.0: <i>unreleased</i></h3> + <ul> + <li>Switch to an improved NEWS file format<br/> + List user-visible changes instead of single commits for a better + high-level overview of differences between libvirt releases + </li> + <li>Various bug fixes and improvements</li>
Should we end with full point when starting with uppercase letter? ACK either way.
+ </ul> + <h3>v2.4.0: Nov 1 2016</h3> <ul> <li>Documentation:<br/> -- 2.7.4
-- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
On Sun, 2016-11-20 at 14:09 +0100, Martin Kletzander wrote:
On Fri, Nov 18, 2016 at 05:16:47PM +0100, Andrea Bolognani wrote:
This entry is meant to both get the ball rolling on the switch and to provide a blueprint of what NEWS file entries are supposed to look like. --- We need to start somewhere, and what better way than talking about the change itself? ;) docs/news.html.in | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/docs/news.html.in b/docs/news.html.in index deeee4d..fca1e29 100644 --- a/docs/news.html.in +++ b/docs/news.html.in @@ -16,6 +16,15 @@ to gauge progress. </p> + <h3>v2.5.0: <i>unreleased</i></h3> + <ul> + <li>Switch to an improved NEWS file format<br/> + List user-visible changes instead of single commits for a better + high-level overview of differences between libvirt releases + </li> + <li>Various bug fixes and improvements</li> Should we end with full point when starting with uppercase letter?
I think it looks better without the full stop inside an unordered list, so I'm going to leave it alone for now. My main concern right now is getting *something* in the NEWS file, we can tweak the style with a later patch. It will probably be a good idea to go over all the entries for a release right before the release happens anyway.
ACK either way.
Pushed, thanks! -- Andrea Bolognani / Red Hat / Virtualization
participants (2)
-
Andrea Bolognani -
Martin Kletzander