Well, I guess I didn’t read closely enough (I was a bit rushed when I first looked at this — mea culpa). Major version bumps have already happened. I started reading at Ansible.netcommon broken with Ansible Core 2.19.0 - #22 by KB-perByte from @KB-perByte from last week about the planned major release bumps but didn’t immediately realize that they had already happened — despite feedback from other steering committee members. It sounds like this was a miscommunication, but I find it frustrating that it seems our policies are not being followed. This now creates extra work for the Ansible release managers, as we have to manually reset the ansible-12.build file to accommodate the major version bumps in these collections that occurred after the beta1 release when the feature freeze started.
1 Like