Open felixfontein opened 4 years ago
Sounds good
I've just released community.docker 0.1.0. You can find the current state of the docs here: https://ansible.fontein.de/collections/community/docker/index.html
I didn't find any problems yet (except #17, which isn't a real problem yet since support on Ansible's side is also missing, at least in the stable-2.10 branch). How about releasing 1.0.0 next week, let's say on Tuesday?
I didn't find any problems yet (except #17, which isn't a real problem yet since support on Ansible's side is also missing, at least in the stable-2.10 branch). How about releasing 1.0.0 next week, let's say on Tuesday?
I think it's a good idea to release 1.0.0 then work on changes and new features (including handling the requests we have in queue)
Since nobody reported anything, I'm now working on the 1.0.0 release.
1.0.0 has been released :tada: I've already created a PR for inclusion in Ansible 2.10: ansible-community/ansible-build-data#36
I released 1.0.1 with bugfix #43.
In case you're wondering, Ansible is switching from Shippable to Azure Pipelines. I'll continue @gundalow's work over the weekend, and hopefully we'll have proper (i.e. all green) CI back next week. (For the release I ignored AZP and only looked at Shippable in case you wonder. And the problems with AZP come from the fact that AZP runs docker containers in a user-defined network.)
I think it would be great if we could release 1.1.0 with a bunch of new features and bugfixes by January 4th, so it can get included in the next Ansible 2.10.5 release (ETA January 5th).
The last open PR is merged, I'll create a 1.1.0 release somewhen today.
1.1.0 has been released :tada: The next expected release is 1.2.0; if some bugfixes are there earlier without a new feature, they will be released as 1.1.1.
I'll work on a 1.2.0 release later today - we have one feature and two bugfixes, and the last Ansible 2.10.x release will be on one of the next days.
1.2.0 has been released!
I'll do a 1.2.1 bugfix release now to get #76 out.
1.2.1 has been released. The next planned release is 1.3.0 (as before).
1.2.2 has been released, addressing CVE-2021-20191. The next planned release is 1.3.0 (as before).
1.3.0 has been released. The next expected release is 1.4.0.
1.4.0 has been released with a security fix, which potentially breaks a use-case of docker_swarm
. The next expected release is 1.5.0.
Since #96 and #119 do not seem to make progress, I'll release 1.5.0 today including the recent bugfixes and features, so it can be included in Ansible 3.3.0 which is to be released this week.
1.5.0 has been released. The next expected release is 1.6.0.
I plan to release 1.6.0 latest by the beginning of next week, hopefully with both #96 and #135 included. (If released by May 11th, this will make it both into the last Ansible 3.x.0 release, and into Ansible 4.0.0.)
1.6.0 has been released. The next expected release is 1.7.0.
I'll release 1.6.1 with #143 later today. (It also contains the scenario guide from ansible/ansible.) Once #142 is fixed, that will probably go into a 1.6.2 release, since I don't think that will get fixed today.
1.6.1 has been released. The next planned release is 1.7.0, though I expect there will probably be a 1.6.2.
I'll create a 1.6.2 release beginning of next week with some doc fixes.
In fact, it probably will end up as 1.7.0 since one of the doc fixes extended in a small feature (allow to tag images by ID).
1.7.0 has been released. Next expected release is 1.8.0, though I guess 1.7.1 will slip in before that :)
I'm currently planning for 1.8.0 by the end of this week / beginning of next week. It should include #157 and #159. If someone wants to fix / improve something else until then, feel free to do so :)
According to the Ansible 5 roadmap, community.docker 2.0.0 needs to be released by October 25th (https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_5.html) to get included in Ansible 5.0.0. I guess we can start somewhen in September by creating a stable-1
branch and start doing backwards incompatible changes in the main
branch for 2.0.0.
I released 1.8.0. Thanks to @Ajpantuso for all the additions! :tada:
I'm planning to release 1.9.0 tomorrow, if nobody complains.
1.9.0 has been released!
According to the Ansible 5 roadmap, community.docker 2.0.0 needs to be released by October 25th (https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_5.html) to get included in Ansible 5.0.0. I guess we can start somewhen in September by creating a
stable-1
branch and start doing backwards incompatible changes in themain
branch for 2.0.0.
The schedule has been postponed a bit, the new deadline is November 8th. Let's still start this in September, but maybe more at its end :)
I'm planning to do a 1.9.1 release this weekend, to get #192 and #194 out.
1.9.1 has been released.
@WojciechowskiPiotr @Ajpantuso do you have more features planned for a last minor release before 2.0.0? If not, I'd like to release 1.10.0 soon, create a stable-1 branch, merge #210, begin bumping the version in galaxy.yml to 2.0.0, and then merge #163 and potentially other PRs someone wants to get into 2.0.0. What do you think?
@WojciechowskiPiotr @Ajpantuso do you have more features planned for a last minor release before 2.0.0?
Nothing from me, please proceed.
Once #217 is merged I'll release 1.10.0 and start the branching.
1.10.0 has been released, and stable-1 now exists :tada:
@WojciechowskiPiotr @Ajpantuso is there anything you want included in the 2.0.0 release? Otherwise we should start thinking of actually releasing that one :) I'd suggest to wait 1-2 weeks, just in case we come up with something, and then get it out so people can test it a bit before we have feature freeze in Ansible 5.
is there anything you want included in the 2.0.0 release?
If I had bandwidth I'd try and do something about the compose issue, but I don't so I'm good to proceed with 2.0.0.
If nobody minds, I'll do the 2.0.0 release by the end of next week.
If nobody minds, I'll do the 2.0.0 release by the end of next week.
I have nothing right now. One is in the queue to deploy but I think it can be added after the 2.0.0 release.
2.0.0 is released! :tada:
I'll create a bugfix release this weekend to get some docs fixes out. If anyone wants to get another fix in until then, feel free :)
1.10.1 and 2.0.1 have been released with docs fixes.
I'll probably create a new bugfix release over the next days (for #243). If someone wants to get something else in, please ping me.
1.10.2 and 2.0.2 have been released with bugfixes for the community.docker.nsenter
and community.docker.docker_api
connection plugins and the community.docker.docker_container_exec
module.
1.10.3 and 2.1.0 have been released with some bugfixes, and bugfixes and new features (mainly for docker_container_exec
) for the 2.1.0 release.
1.10.4 and 2.1.1 have been releaed to fix an issue with the previous 1.10.3 and 2.1.0 releases.
I'm planning to release 2.2.0 and 1.10.5 before Tuesday, either with or without #297.
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 form
main
branch, as described here: https://github.com/ansible/community/wiki/ReleasingCollections#releasing-without-release-branches-for-smaller-collectionsOnce 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. We currently have some deprecation removals scheduled for 2.0.0 (see #1). Maybe scheduling 2.0.0 roughly for Ansible 2.12 (i.e. next summer) would be a good idea.(This is essentially what other collections I work on are doing, like community.crypto, community.sops and community.routeros.)
About the next release(s): I plan to merge #1 today or tomorrow and then release an initial 0.1.0. I would suggest we quickly release a 1.0.0 version, so we can get it included in Ansible 2.10. We should do some testing with the current 0.1.0 release, maybe add bugfixes (or even features), if necessary release a 0.2.0 first, but not wait too long until 1.0.0.
What do you think?