- 18 6月, 2020 1 次提交
-
-
由 Daniel Henrique Barboza 提交于
Although this can be considered a new feature, from the user standpoint is more of a QoL improvement. Suggested-by: NMichal Privoznik <mprivozn@redhat.com> Signed-off-by: NDaniel Henrique Barboza <danielhb413@gmail.com> Reviewed-by: NMichal Privoznik <mprivozn@redhat.com>
-
- 10 6月, 2020 1 次提交
-
-
由 Michal Privoznik 提交于
Signed-off-by: NMichal Privoznik <mprivozn@redhat.com> Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
-
- 05 6月, 2020 2 次提交
-
-
由 Andrea Bolognani 提交于
Until libvirt 2.5.0 we didn't have a real process for release notes in place, and we just published the list of commits that had made it into each release, dividing them into categories that mostly matched the sections we use today. Those documents haven't been relevant for years, but they're still in the git repository and collectively take up almost 2 MiB of disk space. Let's import the only valuable piece of information they contain, the release date for each libvirt versions, into the current document and then drop them for good. Signed-off-by: NAndrea Bolognani <abologna@redhat.com> Reviewed-by: NJán Tomko <jtomko@redhat.com>
-
由 Andrea Bolognani 提交于
Instead of storing release notes as XML and then converting them to HTML and ASCII at build time using XSLT and a custom script, we can use reStructuredText as both the source and ASCII representation and generate HTML from it using the same tooling we already use for the rest of the documentation. Signed-off-by: NAndrea Bolognani <abologna@redhat.com> Reviewed-by: NJán Tomko <jtomko@redhat.com>
-