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

Open
Andersson007 opened this issue Sep 24, 2020 · 16 comments
Open

Release plan #17

Andersson007 opened this issue Sep 24, 2020 · 16 comments

Comments

@Andersson007
Copy link
Contributor

Andersson007 commented Sep 24, 2020

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 Andersson007 pinned this issue Sep 24, 2020
@Andersson007
Copy link
Contributor Author

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

@markuman
Copy link
Member

community.proxysql version 1.1.0 has been released.

@Andersson007
Copy link
Contributor Author

@markuman thanks for releasing!

@markuman
Copy link
Member

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

@markuman
Copy link
Member

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

@ls-michielrensen
Copy link
Contributor

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

@markuman
Copy link
Member

@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
#73 #71

@markuman
Copy link
Member

Done. Theoretically we can start releasing 1.3.0

Or we wait for the hackerthon #68
The benefit is, that the work of the hackerthon will be released shortly afterwards.

What do you think @Andersson007?

@Andersson007
Copy link
Contributor Author

@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
Copy link
Contributor Author

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

@Andersson007
Copy link
Contributor Author

1.3.0 has just been released

@markuman
Copy link
Member

markuman commented Jan 5, 2022

Tomorrow I will release 1.3.1

@markuman
Copy link
Member

markuman commented Jan 6, 2022

1.3.1 has just been released

@markuman
Copy link
Member

community.proxysql 1.4.0 can be released soon:

@markuman
Copy link
Member

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

@markuman
Copy link
Member

markuman commented Jan 4, 2023

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

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

No branches or pull requests

3 participants