-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release plan #81
Comments
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. |
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, |
Oh yes, thanks for the bump. I will arrange a release once #157 is merged, which I expect will be this week. |
|
@csmart, many thanks for the new release 1.3.0. |
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 ansible-collections/community.crypto#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.
The text was updated successfully, but these errors were encountered: