Release plan

[Andersson007]

SUMMARY

(partially copied from ansible-collections/community.crypto#74 , thanks to @felixfontein)

We announce the releases of the community.kubevirt collection here.

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]

@snecklifter i can see several fragments in the changelog/fragments directory and the last release was in January.
Do you think if we can release the next version (minor one, I suppose)?

[snecklifter]

@Andersson007 sure, would be good to include the couple of fixes I did in a release.