Release, versioning, and deprecation policy

[displague]

Originally from ansible-collections/ansible-inclusion#15

has a policy of releasing, versioning and deprecation announced to contributors and users in some way

Comment: cannot find, MUST be fixed (via an issue for example, see examples in collections, such issues are usually pinned)

Guidance is provided about how Ansible collections should handle versioning and deprecation:
https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst#contributor-workflow

This project offers a CHANGELOG at https://github.com/equinix/ansible-collection-metal/blob/main/CHANGELOG.rst describing releases. It is possible to follow changes to the changelog by subscribing to https://github.com/equinix/ansible-collection-metal/releases.atom, or "Watching" releases using the GitHub UI.

There is no predefined roadmap or timeline for new features or upcoming releases.

New semver releases will be made as demands based on incoming issues or enhancements and the maintainers perceived need to distribute the resultant changes. See https://semver.org/#semantic-versioning-specification-semver for more details.

Maintainers may update this issue as needed