community.proxysql icon indicating copy to clipboard operation
community.proxysql copied to clipboard

Published 20 hours ago • verified publisher icon ansible-collections

Release plan

Open Andersson007 opened this issue 5 years ago • 16 comments

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

Andersson007 avatar Sep 24 '20 08:09 Andersson007

we are going to release community.proxysql 1.1.0 tomorrow (23.07.2021)

Andersson007 avatar Jul 22 '21 12:07 Andersson007

community.proxysql version 1.1.0 has been released.

markuman avatar Jul 23 '21 07:07 markuman

@markuman thanks for releasing!

Andersson007 avatar Jul 23 '21 08:07 Andersson007

we are going to release community.proxysql 1.2.0 tomorrow (18.08.2021)

markuman avatar Aug 17 '21 09:08 markuman

community.proxysql version 1.2.0 has been released - https://github.com/ansible-collections/community.proxysql/blob/main/CHANGELOG.rst#v1-2-0

markuman avatar Aug 18 '21 11:08 markuman

What about releasing v1.3.0, I'd like to use it instead of my own patch ;-)

ls-michielrensen avatar Sep 24 '21 11:09 ls-michielrensen

@ls-michielrensen We can do it next week I guess.
The only thing that is left for 1.3.0 is fixing a backwarts compatible bug that was introduced with 1.1.0
https://github.com/ansible-collections/community.proxysql/pull/73 https://github.com/ansible-collections/community.proxysql/issues/71

markuman avatar Sep 24 '21 12:09 markuman

Done. Theoretically we can start releasing 1.3.0

Or we wait for the hackerthon https://github.com/ansible-collections/community.proxysql/issues/68
The benefit is, that the work of the hackerthon will be released shortly afterwards.

What do you think @Andersson007?

markuman avatar Sep 28 '21 10:09 markuman

@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. If nobody picks up the issue during the hackathon, we can solve it later.

Andersson007 avatar Sep 28 '21 14:09 Andersson007

I'm gonna release 1.3.0 now. You have 2 minutes since this message is posted if you wanna stop me:)

Andersson007 avatar Sep 30 '21 11:09 Andersson007

1.3.0 has just been released

Andersson007 avatar Sep 30 '21 12:09 Andersson007

Tomorrow I will release 1.3.1

markuman avatar Jan 05 '22 19:01 markuman

1.3.1 has just been released

markuman avatar Jan 06 '22 08:01 markuman

community.proxysql 1.4.0 can be released soon:

  • drop ansible <= 2.10 #100
  • fix installation role using proxysql 2.4.0 #101

markuman avatar May 21 '22 09:05 markuman

1.4.0 has just been released.
Thanks @jpiron for your contribution.

markuman avatar May 25 '22 08:05 markuman

1.5.0 has just been released.
Thanks @jpiron and @squirrel532 for your contributions.

markuman avatar Jan 04 '23 18:01 markuman