# Adjust Ansible 12 release schedule **URL:** \ **Category:** Project Discussions\ **Tags:** release-management, ansible, 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:** 21
**Author:** ![KB-perByte](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/kb-perbyte/32/541_2.png) [@KB-perByte](https://forum.ansible.com/u/KB-perByte)\ **Post date:** [August 20, 2025, 4:16pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/21 "2025-08-20T16:16:12Z")
Hi all, we might have caused a bit of trouble with the major release. > [@Ansible.netcommon broken with Ansible Core 2.19.0](https://forum.ansible.com/t/ansible-netcommon-broken-with-ansible-core-2-19-0/44043/27): > > @felixfontein @mariolenz The concern is real. But we need to bump the dependency to make sure that the platform collection always resolves aka pulls in the correct version of netcommon, to support all versions of ansible-core that we are testing with that is 2.15 - 2.19 and devel, milestone. Now, Core ≤ 2.18 white_check_mark netcommon works fine up to v8.0.1white_check_mark Platform collections (e.g., cisco.ios, cisco.nxos, arista.eos) are not impacted Core = 2.19 cross_mark ne… ^ Based on this, we have always followed a cycle of major releases when a breaking change is fixed or a dependency update is addressed. In this case, it was both. Having received feedback from the Steering Committee Members, and the team being on a clock to make it to the downstream EE build. We had to make a decision. Whether to make a major release or a minor one. But given the regression that was handled, we decided that a major release makes the most sense for us. We are open to updating our practices with any updated policies present. As per the releases that happened, none of them consider any breaking change from a user standpoint. Regards. --- _[View the full topic](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507)._