# Adjust Ansible 12 release schedule **URL:** \ **Category:** Project Discussions\ **Tags:** ansible, release-management, community-wg\ **Created:** [April 3, 2025, 8:22pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507 "2025-04-03T20:22:13Z")\ **Posts on this page:** 1\ **Showing post:** 18
**Author:** ![gotmax23](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gotmax23/32/106_2.png) [@gotmax23](https://forum.ansible.com/u/gotmax23)\ **Post date:** [August 20, 2025, 12:03am UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/18 "2025-08-20T00:03:40Z")
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](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/22) 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. --- _[View the full topic](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507)._