# \[Vote ended on 2025-09-18\] Ansible 13 roadmap

**URL:** <https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367>\
**Category:** Project Discussions\
**Tags:** community, documentation, community-wg\
**Created:** [August 25, 2025, 4:17pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367 "2025-08-25T16:17:43Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**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 25, 2025, 4:17pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/1 "2025-08-25T16:17:43Z")

</div>

I’ve created a draft for a possible [Ansible 13 roadmap](https://github.com/ansible/ansible-documentation/pull/3000).

[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) Please have a look at it.

I’m not sure when we should start a vote on this. Maybe we should wait until `12.0.0rc1` is released, or even `12.0.0`.

---

<div class="post-metadata">

**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:** [September 4, 2025, 3:58pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/2 "2025-09-04T15:58:22Z")

</div>

[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) [@release-managers](https://forum.ansible.com/groups/release-managers) This has been published in The Bullhorn only recently. So I think I’ll wait a couple of more days before I start a vote.

The options will be quite simple: Accept or reject. That is, if nobody has a good idea for better ones.

---

<div class="post-metadata">

**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:** [September 9, 2025, 3:52pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/3 "2025-09-09T15:52:05Z")

</div>

Thanks for working on this! I wonder if we should add something like this to the roadmap notes (wordsmithing welcome):

> In the event an unforeseen scenario arises in Ansible Core or a collection included in the Ansible package that would require immediate changes to the release schedule and there is not time before the next release to conduct a formal vote, the Release Management WG can make a decision to adjust the roadmap based on an informal consensus of release managers and Steering Committee members.

This is what we had to when everything fell apart in Ansible 12, so perhaps we should document this in case it happens again.

---

<div class="post-metadata">

**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:** [September 9, 2025, 4:23pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/4 "2025-09-09T16:23:28Z")

</div>

Interesting point @gotmax23. But due to the delayed release of ansible-core 2.19 and, even more so, Ansible 12 I think it would be better to move this to a dedicated discussion.

Let’s get a plan on the dates of the Ansible 13 roadmap first, and discuss your suggestion somewhere else / later. If we have consensus of something you suggest, we can always add it to the Ansible 14 roadmap. Or even to the Ansible 13 roadmap afterwards. I think it’s more important to define some rough dates when we want to release what. Both for us and for the users.

---

<div class="post-metadata">

**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:** [September 9, 2025, 4:28pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/5 "2025-09-09T16:28:13Z")

</div>

Makes sense to me. If there’s no other objections, should we start a vote?

---

<div class="post-metadata">

**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:** [September 9, 2025, 5:02pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/6 "2025-09-09T17:02:24Z")

</div>

Let’s vote on the Ansible 13 roadmap that I’ve proposed.

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/6))_

_Poll ([view on site](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/6))_

---

<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:** [September 9, 2025, 5:50pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/7 "2025-09-09T17:50:24Z")

</div>

> [@gotmax23](#):
>
> Thanks for working on this! I wonder if we should add something like this to the roadmap notes (wordsmithing welcome):
> 
> > In the event an unforeseen scenario arises in Ansible Core or a collection included in the Ansible package that would require immediate changes to the release schedule and there is not time before the next release to conduct a formal vote, the Release Management WG can make a decision to adjust the roadmap based on an informal consensus of release managers and Steering Committee members.
> 
> This is what we had to when everything fell apart in Ansible 12, so perhaps we should document this in case it happens again.

I’m not sure whether this should be part of the roadmap, or rather in the SC rules somewhere (where the voting procedures are defined).

---

<div class="post-metadata">

**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:** [September 10, 2025, 12:19am UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/8 "2025-09-10T00:19:57Z")

</div>

> [@felixfontein](#):
>
> I’m not sure whether this should be part of the roadmap, or rather in the SC rules somewhere (where the voting procedures are defined).

I’d be fine with either and am open to feedback, but I think we should put this somewhere official.

---

<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:** [September 16, 2025, 5:16am UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/9 "2025-09-16T05:16:34Z")

</div>

[@SteeringCommittee](https://forum.ansible.com/groups/steeringcommittee) this vote ends in two days, but so far we only had four SC votes. Can you please take a look and vote? Thanks.

---

<div class="post-metadata">

**Author:** ![samccann](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/samccann/32/18_2.png) [@samccann](https://forum.ansible.com/u/samccann)\
**Post date:** [September 17, 2025, 4:37pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/10 "2025-09-17T16:37:32Z")

</div>

my nickel on the extra text is to add it to the SC docs.

---

<div class="post-metadata">

**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:** [September 18, 2025, 2:47pm UTC](https://forum.ansible.com/t/vote-ended-on-2025-09-18-ansible-13-roadmap/44367/11 "2025-09-18T14:47:04Z")

</div>

There are 9 votes from the SC (so quorum is reached) and 3 from the community. All are positive on the proposed roadmap.

So it looks like we now have a roadmap for Ansible 13 😃
