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)?
4 Likes
CC @release-managers since this means more work for us 
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.
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.
This makes sense to me as well.
For the record: Maintain Ansible 9 for longer than 6 months