Skip to content
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

Open
Andersson007 opened this issue Jul 21, 2021 · 12 comments
Open

Release plan #81

Andersson007 opened this issue Jul 21, 2021 · 12 comments
Labels

Comments

@Andersson007
Copy link
Contributor

Andersson007 commented Jul 21, 2021

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?

  1. Release minor and patch releases whenever we want (like after adding new features or fixing bugs). Since this collection is small, there's no need to fix things in advance. Just add features, and after a feature either wait a bit longer for more features/bugs, or make a release.

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.

@Andersson007
Copy link
Contributor Author

I'm gonna release version 1.0.2 tomorrow (22.07.2021).

@Andersson007
Copy link
Contributor Author

community.libvirt 1.0.2 has just been released

@Andersson007
Copy link
Contributor Author

Andersson007 commented Aug 26, 2021

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!

@thinkl33t
Copy link
Contributor

Can we push 1.1.1 (or 1.2.0) with the changes from this weekend? :)

@Andersson007
Copy link
Contributor Author

There's also a minor change made since the last release, so it should be 1.2.0:)

@bturmann
Copy link
Contributor

bturmann commented Sep 5, 2023

Hi,
can we release 1.2.x?

@csmart
Copy link
Collaborator

csmart commented Sep 5, 2023

Oh yes, thanks for the bump. I will arrange a release once #157 is merged, which I expect will be this week.

@csmart
Copy link
Collaborator

csmart commented Sep 19, 2023

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 #160

@csmart
Copy link
Collaborator

csmart commented Sep 25, 2023

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.

@bturmann
Copy link
Contributor

@csmart, many thanks for the new release 1.3.0.

@leegarrett
Copy link

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.

@csmart
Copy link
Collaborator

csmart commented Apr 25, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants