# 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:** 20\ **Page:** 1
**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:** [April 3, 2025, 8:22pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/1 "2025-04-03T20:22:13Z")
Now that there as been a first announcement on ansible-core 2.19’s delay ([ansible-core 2.19 release schedule update](https://forum.ansible.com/t/41504)), we should think about Ansible 12’s release schedule ([Ansible project 12.0 — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_12.html#release-schedule)). I think it would be best to simply adjust it so that it aligns with the new dates of ansible-core, i.e.: - ansible-core beta releases get a Ansible alpha release a day later; - ansible-core’s rc releases gets Ansible beta releases a day later; - and ansible-core 2.19.0 GA gets Ansible feature freeze a day later; - Ansible 12.0.0rc1 a week after that; - and 1-2 weeks later 12.0.0 comes out. WDYT? And how should we adjust the release schedule at [Ansible project 12.0 — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_12.html#release-schedule)? Simply strike through the dates and add an info box that basically says the above (in nicer wording), and replace the dates once we have more exact ones for ansible-core? ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [April 4, 2025, 2:43pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/2 "2025-04-04T14:43:54Z")
As far as I can see, the [ansible-core 2.19 roadmap](https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_19.html) hasn’t changed yet. I’m not sure if we should change any dates if we don’t have ones from core that we can point to. Maybe start with an info box stating a delay because of and mentioning [ansible-core 2.19 release schedule update](https://forum.ansible.com/t/41504)? At the very least, we should announce both here on the forum and on Bullhorn (maybe simply mentioning the forum post) that we will delay Ansible 12 because of the ansible-core 2.19 release schedule update. ---
**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:** [April 4, 2025, 6:24pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/3 "2025-04-04T18:24:38Z")
> [@mariolenz](#): > > As far as I can see, the [ansible-core 2.19 roadmap](https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_19.html) hasn’t changed yet. I’m not sure if we should change any dates if we don’t have ones from core that we can point to. That’s why I suggested to follow a generic pattern that is based on ansible-core pre-releases, instead of fixing dates 🙂 > [@mariolenz](#): > > Maybe start with an info box stating a delay because of and mentioning [ansible-core 2.19 release schedule update](https://forum.ansible.com/t/41504)? > > At the very least, we should announce both here on the forum and on Bullhorn (maybe simply mentioning the forum post) that we will delay Ansible 12 because of the ansible-core 2.19 release schedule update. Definitely! ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [April 5, 2025, 10:54am UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/4 "2025-04-05T10:54:20Z")
> [@felixfontein](#): > > And how should we adjust the release schedule at [Ansible project 12.0 — Ansible Community Documentation](https://docs.ansible.com/ansible/devel/roadmap/COLLECTIONS_12.html#release-schedule)? Simply strike through the dates and add an info box that basically says the above (in nicer wording), and replace the dates once we have more exact ones for ansible-core? I don’t have a better idea at the moment and this suggestion sounds good to me. Additionally, how about documenting our usual approach (or a “general roadmap”) like in your list: - ansible-core beta releases get a Ansible alpha release a day later - ansible-core’s rc releases gets Ansible beta releases a day later and so on in [Ansible Roadmap](https://docs.ansible.com/ansible/devel/roadmap/ansible_roadmap_index.html)? ---
**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:** [April 5, 2025, 3:23pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/5 "2025-04-05T15:23:27Z")
I started drafting that: [Describe general Ansible major version release schedule; announce that Ansible 12.0.0's release schedule gets delayed according to ansible-core 2.19.0's release schedule by felixfontein · Pull Request #2490 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2490) ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [April 9, 2025, 4:59pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/6 "2025-04-09T16:59:10Z")
> [@felixfontein](#): > > I started drafting that: [Describe general Ansible major version release schedule; announce that Ansible 12.0.0’s release schedule gets delayed according to ansible-core 2.19.0’s release schedule by felixfontein · Pull Request #2490 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2490) I’ve commented. Anyone else from the [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) who might want to have a look? ---
**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:** [April 12, 2025, 9:29am UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/7 "2025-04-12T09:29:07Z")
As discussed on Wednesday I’ve repurposed that PR to only add a general release schedule, and removed the changes to the Ansible 12 release schedule. The Ansible 12 release schedule got updated in [Adjust Ansible 12 roadmap by felixfontein · Pull Request #2508 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2508) after approval of 7 SC members. So this topic is basically done for now. Thanks everyone! ---
**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:** [May 27, 2025, 8:43pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/8 "2025-05-27T20:43:00Z")
There’s a new delay: according to [Core 2.19 beta extended thru June 30](https://forum.ansible.com/t/43035), ansible-core 2.19.0 GA will be released on July 21st, instead of June 16th. IMO we should adjust Ansible 12’s schedule once more to match ansible-core’s schedule. ---
**Author:** ![nitzmahone](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nitzmahone](https://forum.ansible.com/u/nitzmahone)\ **Post date:** [May 27, 2025, 9:55pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/9 "2025-05-27T21:55:41Z")
Yep, sorry we’re making life difficult there, but I know you understand it’s a lot easier to fine-tune these things before they’re shipped than after 😆 ---
**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:** [May 28, 2025, 6:14pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/10 "2025-05-28T18:14:27Z")
I created a PR: [Adjust Ansible 12's release schedule to ansible-core 2.19's updated schedule by felixfontein · Pull Request #2664 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2664) Since there’s no update yet for the ansible-core 2.19 roadmap, some dates I wasn’t able to fill in yet… ---
**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:** [June 2, 2025, 7:37pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/11 "2025-06-02T19:37:30Z")
How should we proceed with the PR? (There’s still no PR for the ansible-core roadmap.) Should we wait for an update of the ansible-core roadmap, merge my PR as-is, …? ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [June 3, 2025, 3:21pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/12 "2025-06-03T15:21:46Z")
Since our Roadmap follows that of ansible-core, it would be really great if this would be updated first ( **hint** **hint** @nitzmahone). Let’s give them a few more days to do it. ---
**Author:** ![nitzmahone](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nitzmahone](https://forum.ansible.com/u/nitzmahone)\ **Post date:** [June 3, 2025, 3:47pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/13 "2025-06-03T15:47:23Z")
Sorry, been buried in, well, you know- I’ll try to have someone push a doc PR this morning or do it myself… Sivel usually handles the roadmap updates, but he’s been out for a few days. The date shuffle we announced likely puts 2.19.0 on an off-cycle date with the other releases, but that’s OK- gives us a short cycle for 2.19.1, which history shows often ends up releasing early anyway. In any case, the dates we announced are still good and should be reflected on the roadmap soon. Thanks! ---
**Author:** ![nitzmahone](https://avatars.discourse-cdn.com/v4/letter/n/c5a1d2/32.png) [@nitzmahone](https://forum.ansible.com/u/nitzmahone)\ **Post date:** [June 3, 2025, 3:58pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/14 "2025-06-03T15:58:59Z")
> ---
**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:** [June 3, 2025, 6:04pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/15 "2025-06-03T18:04:41Z")
Thanks @nitzmahone, I’ve merged your PR. If nobody objects, I’ll merge my PR (adjusted with the dates as suggested by @mariolenz) soon as well. ---
**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")
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? ---
**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 19, 2025, 9:13pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/17 "2025-08-19T21:13:46Z")
It possible, I would prefer if the other network collections did not have additional major versions. We are a month past the scheduled feature freeze and have already modified our policies, schedules, and tooling to accommodate the network collections once. I would vote to make another exception if absolutely necessary, but it would be great if we could work with the network collection maintainers to find another solution so we can simply update the networking collections to the latest minor version. ---
**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. ---
**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:30am UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/19 "2025-08-20T00:30:29Z")
> [@felixfontein](#): > > 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? To be explicit, I do support including these releases, despite my reservations. What do other [@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) members and [@release-managers](https://forum.ansible.com/groups/release-managers) think? As @felixfontein said, we were supposed to release Ansible 12.0.0b4 this week, so it would be great to reach a consensus about whether to include these newly released collections soon. ---
**Author:** ![mariolenz](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mariolenz/32/108_2.png) [@mariolenz](https://forum.ansible.com/u/mariolenz)\ **Post date:** [August 20, 2025, 3:10pm UTC](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507/20 "2025-08-20T15:10:13Z")
> [@felixfontein](#): > > 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. If they don’t contain any breaking changes, let’s include them. Seems to be the best way forward to me ATM. I still don’t understand why they insist on doing new major releases, though. I didn’t see a good reason for this so far… [Next page](https://forum.ansible.com/t/adjust-ansible-12-release-schedule/41507.md?page=2)