# \[vote ended 2025-04-16\] Make Ansible 11 a "LTS" (similar to Ansible 9)? **URL:** \ **Category:** Project Discussions\ **Tags:** ansible, release-management, templating, community-wg\ **Created:** [March 8, 2025, 9:09am UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851 "2025-03-08T09:09:43Z")\ **Posts on this page:** 16\ **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:** [March 8, 2025, 9:09am UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/1 "2025-03-08T09:09:43Z")
Assuming that Data Tagging is merged for ansible-core 2.19 (which will be the core of Ansible 12), migration of existing roles and playbooks to ansible-core 2.19 and thus Ansible 12 will require a lot of work since there are a lot of existing (mostly bad and common) behaviors that will stop working. To give users more time to migrate, how about extending Ansible 11’s lifetime for another 6 months, similar to what we did with Ansible 9 (the last version to support Python 2.7 and 3.6)? ---
**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:** [March 9, 2025, 4:20pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/2 "2025-03-09T16:20:19Z")
CC [@release-managers](https://forum.ansible.com/groups/release-managers) since this means more work for us 😉 ---
**Author:** ![acozine](https://avatars.discourse-cdn.com/v4/letter/a/ecccb3/32.png) [@acozine](https://forum.ansible.com/u/acozine)\ **Post date:** [March 9, 2025, 4:53pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/3 "2025-03-09T16:53:12Z")
This sounds good to me. That said, I am not involved in packaging releases. I think the folks who do work on the releases should have the final say. ---
**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:** [March 9, 2025, 8:07pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/4 "2025-03-09T20:07:32Z")
I’m not sure if this will be really necessary. On the other hand, I think that the automation to do releases is pretty good (thx @felixfontein!) . We can handle it, so I won’t object. ---
**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:** [March 10, 2025, 11:45pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/5 "2025-03-10T23:45:43Z")
This makes sense to me as well. ---
**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:** [March 11, 2025, 6:44pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/6 "2025-03-11T18:44:46Z")
> [@felixfontein](#): > > To give users more time to migrate, how about extending Ansible 11’s lifetime for another 6 months, similar to what we did with Ansible 9 (the last version to support Python 2.7 and 3.6)? For the record: [Maintain Ansible 9 for longer than 6 months](https://forum.ansible.com/t/2574) ---
**Author:** ![Andersson007](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/andersson007/32/89_2.png) [@Andersson007](https://forum.ansible.com/u/Andersson007)\ **Post date:** [March 19, 2025, 9:25am UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/7 "2025-03-19T09:25:01Z")
SGTM, thanks for bringing this up! ---
**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:23pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/8 "2025-04-03T20:23:54Z")
According to [ansible-core 2.19 release schedule update](https://forum.ansible.com/t/41504) ansible-core 2.19 will have Data Tagging (and will be delayed w.r.t. its original schedule, on which the Ansible 12 release is based). I still think having a Ansible 11 “LTS” with new releases for ~6 additional months (basically until Ansible 13 comes out) is a good idea. Are there objections, or further needs to discuss this? Or should we start a vote on this without further discussion? ---
**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:29pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/9 "2025-04-04T14:29:31Z")
I think a vote is OK. After all, nobody stepped up so far who was deadly against it. However, since it looked for some time that DT might not make it into 2.19 we should make this explicit. Just to make sure in case something really bad happens and core changes their mind. So let’s vote on making Ansible 11 an “LTS” release _if DT makes it into ansible-core 2.19_ yes / no. That way, if core changes their mind again we wouldn’t have the burden to maintain 11 for longer without a good reason, or start another vote to revert this decision. Does this sound OK? ---
**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:25pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/10 "2025-04-04T18:25:11Z")
Sounds good to me. (Still not 20 characters 😉 ) ---
**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:32pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/11 "2025-04-05T15:32:26Z")
The following vote will be open until April 16th during the weekly community meeting. Note that the “Yes” vote is coupled to the [Data Tagging PR](https://github.com/ansible/ansible/pull/84621) being merged. If the PR is not merged into ansible-core 2.19.0, or removed later on before 2.19.0 is released, Ansible 11 will become End of Life once Ansible 12 is out no matter how this vote concludes. _Poll ([view on site](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/11))_ _Poll ([view on site](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/11))_ ---
**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:** [April 5, 2025, 7:08pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/12 "2025-04-05T19:08:21Z")
I voted yes, but it’d be good to have a draft ansible-documentation PR along with this vote that we can merge if/when if data tagging ends up making it in. ---
**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, 7:32pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/13 "2025-04-05T19:32:41Z")
Good idea, I’ve created the PR here: [[WIP] Announce Ansible 11 lifetime extension by felixfontein · Pull Request #2491 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2491) In the PR I wrote that it should only be merged once this vote is accepted _and_ ansible-core 2.19.0 rc1 is out. I guess from that point on it will be quite unlikely that Data Tagging will be removed again before 2.19.0 GA comes out. ---
**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 16, 2025, 5:07pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/14 "2025-04-16T17:07:32Z")
This vote should be closed today. I think we’ve reached quorum, and we have a clear decision 😃 ---
**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 16, 2025, 6:11pm UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/15 "2025-04-16T18:11:52Z")
The vote has been accepted! Thanks a lot. I’ve removed the WIP from [Announce Ansible 11 lifetime extension by felixfontein · Pull Request #2491 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/pull/2491), but marked it as a draft since ansible-core 2.19.0 rc1 isn’t out 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:** [July 1, 2025, 4:40am UTC](https://forum.ansible.com/t/vote-ended-2025-04-16-make-ansible-11-a-lts-similar-to-ansible-9/40851/16 "2025-07-01T04:40:23Z")
ansible-core 2.19.0rc1 has been released: [New Release: ansible-core v2.19.0rc1](https://forum.ansible.com/t/43652) I’m going to merge the PR with the announcement as the last condition has now been satisfied.