# ansible-core 2.19 release schedule update

**URL:** <https://forum.ansible.com/t/ansible-core-2-19-release-schedule-update/41504>\
**Category:** Ecosystem Releases\
**Tags:** ansible-core\
**Created:** [April 3, 2025, 6:46pm UTC](https://forum.ansible.com/t/ansible-core-2-19-release-schedule-update/41504 "2025-04-03T18:46:04Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sivel](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/sivel/32/1198_2.png) [@sivel](https://forum.ansible.com/u/sivel)\
**Post date:** [April 8, 2025, 8:19pm UTC](https://forum.ansible.com/t/ansible-core-2-19-release-schedule-update/41504/2 "2025-04-08T20:19:08Z")

</div>

The Ansible Core team has been able to come to a commitment on the release schedule for ansible-core 2.19 which will include the work known as “Data Tagging”.

| Release Period | Date |
| --- | --- |
| Beta | 2025-04-14 |
| RC | 2025-05-26 |
| GA | 2025-06-16 |

In addition to the above schedule, there are few other details to be aware of:

The [Data Tagging PR](https://github.com/ansible/ansible/pull/84621) will be merged on 2025-04-14, which is the same day as the Beta1 is scheduled for. This is being done to ensure no disruption to various projects with the ansible-core `devel` branch utilized in CI immediately before a weekend.

`stable-2.19` will be branched from `devel` shortly after the merge of DT. The typical pattern of opening the `devel` branch for development of the next release will not be followed. `devel` will continue to be used as the development branch for 2.19, and there will be weekly syncs of `devel` to the `stable-2.19` branch prior to each scheduled beta release.

The `devel` branch will become “unlocked” on 2025-05-26 aligning with the first planned release candidate.

---

_[View the full topic](https://forum.ansible.com/t/ansible-core-2-19-release-schedule-update/41504)._