You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.
Since Ansible-2.10+ is being created from the decentralized collections, there are a lot of policies about the ansible package that are different from the Ansible-2.9 collections. We should call this out to end users in the release notes for ansible-2.10.0.
I think a longer blog post/article and a short blurb with link to the blog post may be the best way to do this.
Release notes:
Ansible-2.10+ is built from collections maintained by a decentralized network of community members. As such, the policies around the Ansible package (deprecation cycles, release schedules, new features, etc) are changing to acommodate what the community contributors need. Please see this blog post for an overview and how to have a say in the direction of policy changes:
Some things to put into the blog post:
Policies that we know have changed:
Deprecations can now be added in the middle of a cycle
Removals may occur without a deprecation. That's up to the collection owner and how their releases sync with the ansible releases
New features can be added in the middle of a cycle.
Where to discuss policy changes [Wednesday Community Meetings]
The text was updated successfully, but these errors were encountered:
Since Ansible-2.10+ is being created from the decentralized collections, there are a lot of policies about the ansible package that are different from the Ansible-2.9 collections. We should call this out to end users in the release notes for ansible-2.10.0.
I think a longer blog post/article and a short blurb with link to the blog post may be the best way to do this.
Release notes:
Some things to put into the blog post:
The text was updated successfully, but these errors were encountered: