-
Notifications
You must be signed in to change notification settings - Fork 90
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 #13
Comments
|
FYI: I will likely release |
1.0.0 has just been released! So the collection will be included in next Ansible releases |
I'm going to release version 1.1.0 on Monday January 18 (if time allows) |
|
|
|
I'm gonna release c.postgresql 1.3.0 now |
|
I'm gonna release c.postgresql 1.4.0 now |
|
i'm gonna release |
|
I'm gonna release c.postgresql 1.6.0 now |
|
@marcosdiez after #173 is slightly corrected and integration tests added, we could merge it and release |
|
@tcraxs @marcosdiez @hunleyd @MichaelDBA ^ is available for installation via Also not having an explicit code approval for #177, we can't proceed with the |
I'm going to release |
|
I'm going to release |
|
I'm going to release |
i'm going to release |
|
i plan on releasing 2.1.2 today |
|
@hunleyd thanks for releasing! |
i plan on releasing community.postgresql 1.7.3 and 2.1.4 today. |
|
As ansible-core 2.14 is scheduled for release in November, I suggest releasing c.p. 3.0.0 in ~December 2022/January 2023 (depending on an actual release date of |
i plan on releasing community.postgresql 1.7.4 and 2.1.5 today. |
Hi @hunleyd, @Andersson007, when do you plan to make the next release? |
There's an open question for @Andersson007 on #303 that I'm holding on. Once he's back from vacation and can advise, we'll cut a release shortly thereafter @betanummeric |
Answered:) feel free to proceed with releasing (if no time, please let me know), thanks! |
@betanummeric would you like to release the collection yourself? I'll provide all the guidelines needed if yes. |
@Andersson007 Ok, let me try it. What do I need to do? |
@betanummeric great, thanks! The process is actually pretty straightforward.
If any questions along the way, feel free to ask. @hunleyd or I should be here. Also you can join https://matrix.to/#/#postgresql:ansible.com on Matrix. |
i plan on releasing 1.7.6 and 2.2.1 today |
i plan on releasing 2.3.1 today |
The community.postgresql collection version 2.3.1 has been released (changelog). Thanks to @vonschultz and @hunleyd ! |
I'm going to release 2.3.2 and 1.7.7 today |
I plan to release 2.4.0 and 1.7.8 today |
The community.postgresql collection versions 1.7.10 and 2.4.2 collection have been released! |
The community.postgresql collection versions versions 1.7.11, 2.4.3, and 3.1.0 were release by @aleksvagachev. Special thanks to @RealGreenDragon and @elpavel who rocked throughout the recent months and out maintainers team: @hunleyd @betanummeric @aleksvagachev @jchancojr for reviewing, merging and releasing stuff. Also added a note for Bullhorn. |
|
as per a discussion with @Andersson007 releases will be announced in the forums instead of this issue going forward. as such, unpinning and closing. |
SUMMARY
(partially copied from ansible-collections/community.crypto#74 , thanks to @felixfontein)
We should decide 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://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.
For release support timeline, refer to README (we should keep it updated)
First release will be 0.1.0
The text was updated successfully, but these errors were encountered: