docs: Go bindings release at the same time as the C library

The actual versioning policy[1] is a bit more nuanced, and in
particular there are scenarios in which the monthly release
is intentionally skipped, but overall it's not inaccurate to
claim that the release cadence of the Go bindings follows the
one of the C library.

[1] https://gitlab.com/libvirt/libvirt-go-module/-/blob/master/VERSIONING.rst

Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>

diff --git a/docs/downloads.rst b/docs/downloads.rst
index c7d4237f66f3525831b305ad3b15f5b6f187cb4d..d3deec554d92f59a07585302a8a792ad33500d22 100644 (file)
--- a/docs/downloads.rst
+++ b/docs/downloads.rst
@@ -261,7 +261,7 @@ The core libvirt module follows a time based plan, with releases made once a
 month on the 1st of each month give or take a few days. The only exception is at
 the start of the year where there are two 6 weeks gaps (first release in the
 middle of Jan, then skip the Feb release), giving a total of 11 releases a year.
-The Python and Perl modules will aim to release at the same time as the core
+The Python, Perl and Go modules will aim to release at the same time as the core
 libvirt module. Other modules have independent ad-hoc releases with no fixed
 time schedule.