During the Ansible 12 release cycle, we communicated to collection maintainers far in advance of the release by mass filing issues that major changes were expected in Core 2.19 and that they should make sure their collections were tested and compatible. I’m not sure if we weren’t clear enough about when this work had to be completed by (i.e., by the Ansible 12 feature freeze) or if the issues were just ignored or if there were other RH-internal factors at play, but several collections were not compatible with Core 2.19 in time for the Ansible 12 feature freeze, and we only found out about this after fact.
Overall, this situation was not ideal, and it created schedule delays and extra work for the release managers and last-minute decisions that the Release Management WG had to make without a complete formal vote from the Steering Committee. I created this thread to have a retrospective and to figure out ways to improve communication with collection maintainers and prevent something like this from happening in the future.
References: