Release plan

[felixfontein]

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-collections

Once 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?

[WojciechowskiPiotr]

Sounds good

[felixfontein]

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

[felixfontein]

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?

[WojciechowskiPiotr]

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)

[felixfontein]

Since nobody reported anything, I'm now working on the 1.0.0 release.

[felixfontein]

1.0.0 has been released 🎉 I've already created a PR for inclusion in Ansible 2.10: ansible-community/ansible-build-data#36

[felixfontein]

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.)

[felixfontein]

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).

[felixfontein]

The last open PR is merged, I'll create a 1.1.0 release somewhen today.

[felixfontein]

1.1.0 has been released 🎉 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.

[felixfontein]

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.

[felixfontein]

1.2.0 has been released!

[felixfontein]

I'll do a 1.2.1 bugfix release now to get #76 out.