Release plan

[Andersson007]

trafficstars

SUMMARY

(partially copied from https://github.com/ansible-collections/community.crypto/issues/74)

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?

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

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.

[Andersson007]

a tentative date of release 1.1.0 is 30.07.2021

[Andersson007]

as everything that was planned for inclusion in the release is ready, I'm gonna release 1.1.0 now.

[Andersson007]

community.rabbitmq 1.1.0 has been release and is available to install now via ansible-galaxy or tarball from Galaxy. It'll also be included in the next ansible package release.

[odyssey4me]

Thanks @Andersson007 for facilitating all this, it really helps things move along!

[Andersson007]

@odyssey4me the Ansible rabbitmq community is always welcome! :)

[Andersson007]

I'm happy to announce that the registration (free) for the Ansible Contributor Summit is open. See the registration page for details. Please register. See you at the summit!

[Im0]

Releasing v1.2.3 ( #143 ) shortly.