# Branching the docs for stable-2.19

**URL:** <https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653>\
**Category:** Project Discussions\
**Tags:** documentation, dawgs-meeting\
**Created:** [April 10, 2025, 11:46am UTC](https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653 "2025-04-10T11:46:45Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\
**Post date:** [April 10, 2025, 11:46am UTC](https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653/1 "2025-04-10T11:46:45Z")

</div>

Hey everyone,

Yet another discussion thread related to stable-2.19. @samccann and I were chatting about how we should branch `ansible/ansible-documentation` according to the release schedule outlined in [ansible-core 2.19 release schedule update - #2 by sivel](https://forum.ansible.com/t/ansible-core-2-19-release-schedule-update/41504/2)

Rather than branching the `devel` branch in the docs repo to `stable-2.19` when the beta release occurs on 2025-04-14, it seems like a good idea to cut the `stable-2.19` branch for docs when the RC lands on 2025-05-26.

Branching docs for the RC follows the “usual” approach to cut the new stable branch for docs when development for new features starts happening on `devel`.

What do folks think?

---

<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:** [April 15, 2025, 2:39am UTC](https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653/2 "2025-04-15T02:39:54Z")

</div>

Apologizes, I missed this before I filed [Branch for stable-2.19 · Issue #2519 · ansible/ansible-documentation · GitHub](https://github.com/ansible/ansible-documentation/issues/2519). I don’t think it makes sense to hold off on this based on when new feature development starts or some other distinction. I think it’ll only create confusion. We’ve always kept the branches in the docs repo in sync with Core, and our tooling assumes this holds true.

---

<div class="post-metadata">

**Author:** ![oranod](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/oranod/32/1434_2.png) [@oranod](https://forum.ansible.com/u/oranod)\
**Post date:** [April 15, 2025, 8:11am UTC](https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653/3 "2025-04-15T08:11:34Z")

</div>

+1 from me @gotmax23 thanks for that. I probably should have pinged you directly in the topic…

---

<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:** [April 15, 2025, 3:23pm UTC](https://forum.ansible.com/t/branching-the-docs-for-stable-2-19/41653/4 "2025-04-15T15:23:59Z")

</div>

Discussed in DaWGs and general agreement to branch the docs now. Thanks everyone!