[libvirt] [PATCH v3.2-maint 0/2] Maintenance branch details
So I just created v3.2-maint with one rather important back-port. This is what I would've pushed with it, but I'd rather know the opinions on whether one or both ideas are stupid. Thanks. Martin Kletzander (2): Maintenance branch version bump docs: Add vz driver typo fix to news.xml configure.ac | 2 +- docs/news.xml | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) -- 2.12.2
Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- configure.ac | 2 +- docs/news.xml | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 08051d53aa0a..693791c6015d 100644 --- a/configure.ac +++ b/configure.ac @@ -16,7 +16,7 @@ dnl You should have received a copy of the GNU Lesser General Public dnl License along with this library. If not, see dnl <http://www.gnu.org/licenses/>. -AC_INIT([libvirt], [3.2.0], [libvir-list@redhat.com], [], [http://libvirt.org]) +AC_INIT([libvirt], [3.2.1], [libvir-list@redhat.com], [], [http://libvirt.org]) AC_CONFIG_SRCDIR([src/libvirt.c]) AC_CONFIG_AUX_DIR([build-aux]) AC_CONFIG_HEADERS([config.h]) diff --git a/docs/news.xml b/docs/news.xml index 6838f1514c21..5aeec5fc49ae 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -32,6 +32,13 @@ --> <libvirt> + <release version="v3.2.1" date="unreleased"> + <section title="Bug fixes"> + <change> + <summary/> + </change> + </section> + </release> <release version="v3.2.0" date="2017-04-02"> <section title="New features"> <change> -- 2.12.2
Signed-off-by: Martin Kletzander <mkletzan@redhat.com> --- docs/news.xml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/news.xml b/docs/news.xml index 5aeec5fc49ae..cad3f68019a2 100644 --- a/docs/news.xml +++ b/docs/news.xml @@ -35,7 +35,9 @@ <release version="v3.2.1" date="unreleased"> <section title="Bug fixes"> <change> - <summary/> + <summary> + Fix a typo in vz driver causing a build failure + </summary> </change> </section> </release> -- 2.12.2
On Tue, Apr 04, 2017 at 03:46:36PM +0200, Martin Kletzander wrote:
So I just created v3.2-maint with one rather important back-port. This is what I would've pushed with it, but I'd rather know the opinions on whether one or both ideas are stupid. Thanks.
So, the website only publishes news.html for the stable branch. Cole manually writes release notes for stable versions in the wiki: http://wiki.libvirt.org/page/Maintenance_Releases So I guess news.xml changes would merely get added into the auto-generated NEWS file. Possibly useful for users, but a little bit hidden until you've got the tar.xz unpacked. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
On Tue, Apr 04, 2017 at 02:51:19PM +0100, Daniel P. Berrange wrote:
On Tue, Apr 04, 2017 at 03:46:36PM +0200, Martin Kletzander wrote:
So I just created v3.2-maint with one rather important back-port. This is what I would've pushed with it, but I'd rather know the opinions on whether one or both ideas are stupid. Thanks.
So, the website only publishes news.html for the stable branch.
Cole manually writes release notes for stable versions in the wiki:
http://wiki.libvirt.org/page/Maintenance_Releases
So I guess news.xml changes would merely get added into the auto-generated NEWS file. Possibly useful for users, but a little bit hidden until you've got the tar.xz unpacked.
Well, mainly easier to create the release notes for Cole (or whoever will be releasing this, if anyone). That was my main goal, not that we would make use of the generated file anywhere on the page.
Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://entangle-photo.org -o- http://search.cpan.org/~danberr/ :|
participants (2)
-
Daniel P. Berrange -
Martin Kletzander