Open Andersson007 opened 3 years ago
I'm gonna release version 1.0.2 tomorrow (22.07.2021).
community.libvirt 1.0.2 has just been released
I'm happy to announce that the registration (free) for the Ansible Contributor Summit is open. See the registration page for details. Please register. See you at the summit!
Can we push 1.1.1 (or 1.2.0) with the changes from this weekend? :)
There's also a minor change made since the last release, so it should be 1.2.0:)
Hi, can we release 1.2.x?
Oh yes, thanks for the bump. I will arrange a release once https://github.com/ansible-collections/community.libvirt/pull/157 is merged, which I expect will be this week.
Pipeline issues have been merged in #158 and #157 has been merged, so we are unblocked now to do a release, which is the next priority https://github.com/ansible-collections/community.libvirt/pull/160
1.3.0
has been tagged and is now available on Galaxy, thank you to everyone for your contributions towards this release! Please let me know if you have any issues.
@csmart, many thanks for the new release 1.3.0.
Time for a new release? I've seen that #147, #156, and #162 have been merged, and I'd prefer to drop them from the Debian package of ansible-community by pulling an upstream update.
Hi @leegarrett , happy to look at another release if needed. I actually haven't merged #162 yet, see my comments on that MR. I think the others should be available already in v1.3.0? What version are you packaging for Debian?
SUMMARY
(partially copied from https://github.com/ansible-collections/community.crypto/issues/74)
We should decide eventually on how to release this collection (w.r.t. versioning). Small collections like this one don't need a complex plan like the one for community.general and community.network. So how about the following?
I suggest releasing without branching https://docs.ansible.com/ansible/devel/community/collection_contributors/collection_release_without_branches.html
Once we release a 2.0.0 (with some breaking change relative to 1.x.y), we can have a stable-1 branch so we can backport bugfixes (or even features) if needed, and release more 1.x.y versions.