Branching the docs for stable-2.19

Project Discussions
,
1

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

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?

2

Apologizes, I missed this before I filed Branch for stable-2.19 · Issue #2519 · ansible/ansible-documentation · GitHub. 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.

1 Like
3

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

4

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