# Adjust Ansible 12 release schedule

**URL:** <https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507>\
**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:** 16

<div class="post-metadata">

**Author:** ![felixfontein](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/felixfontein/32/7530_2.png) [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Post date:** [August 19, 2025, 8:41pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/16 "2025-08-19T20:41:22Z")

</div>

ansible-core 2.19.0rc1 has been released, and we should be releasing a new 12.0.0b4 release soon. (It is mainly waiting for a change in antsibull-build to be reviewed, merged, and a new release of that created.)

Now there’s another thing we need a decision on: as you can read up in [Ansible.netcommon broken with Ansible Core 2.19.0](https://forum.ansible.com/t/44043) (see the bottom posts), several network collections got a new major release. (So far arista.eos, cisco.ios, cisco.iosxr, cisco.nxos, and junipernetworks.junos have new major releases.) These major releases bump the ansible.netcommon dependency, and besides some bugfixes or features, but seem to have no breaking change. Do we want to include these in Ansible 12.0.0? While we wanted to not have breaking changes if we can avoid it for Ansible 12.0.0, which usually means no major version bump for already included collections, these could be acceptable since they do not actually contain breaking changes. [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) what do you think?

---

_[View the full topic](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507)._