On Wed, Sep 27, 2023 at 07:46:22PM +0200, Andrea Bolognani wrote: > 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@xxxxxxxxxx> > --- The caveats around skipping releases for Go also apply to the Perl and Python too. Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> > docs/downloads.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/docs/downloads.rst b/docs/downloads.rst > index c7d4237f66..d3deec554d 100644 > --- 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. > > -- > 2.41.0 > With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
