-
Notifications
You must be signed in to change notification settings - Fork 26
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 #17
Comments
we are going to release community.proxysql 1.1.0 tomorrow (23.07.2021) |
|
@markuman thanks for releasing! |
we are going to release community.proxysql 1.2.0 tomorrow (18.08.2021) |
|
What about releasing |
@ls-michielrensen We can do it next week I guess. |
Done. Theoretically we can start releasing 1.3.0 Or we wait for the hackerthon #68 What do you think @Andersson007? |
@markuman , as the issue is just a refactoring and won't affect users, feel free to release 1.3.0 as soon as you like. |
I'm gonna release 1.3.0 now. You have 2 minutes since this message is posted if you wanna stop me:) |
1.3.0 has just been released |
Tomorrow I will release 1.3.1 |
1.3.1 has just been released |
community.proxysql 1.4.0 can be released soon:
|
1.5.0 has just been released. |
SUMMARY
SUMMARY
(partially copied from ansible-collections/community.crypto#74 , thanks to @felixfontein)
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?
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://github.com/ansible/community-docs/blob/main/releasing_collections_without_release_branches.rst
Breaking changes don't work with this schema but we might change the approach and start releasing from branches when needed.
cc @bmildren
The text was updated successfully, but these errors were encountered: