Skip to content

Fix a few examples in docs that are not 2.19 compatible #2581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: devel
Choose a base branch
from

Conversation

sivel
Copy link
Member

@sivel sivel commented Apr 29, 2025

Fix a few examples in docs that are not 2.19 compatible

@sivel sivel marked this pull request as draft April 29, 2025 17:20
@oraNod oraNod added the backport-2.19 Automatically create a backport for the stable-2.19 branch label Apr 29, 2025
@sivel sivel marked this pull request as ready for review April 29, 2025 17:39
@sivel sivel marked this pull request as draft April 29, 2025 17:48
@sivel sivel marked this pull request as ready for review April 29, 2025 17:51
@gotmax23 gotmax23 requested review from samccann and oraNod April 29, 2025 22:49
@samccann
Copy link
Contributor

samccann commented May 6, 2025

@sivel - Should these be backported to other releases so we are showing the correct content in 2.16-2.18 as well?

@sivel
Copy link
Member Author

sivel commented May 6, 2025

I'm not sure I would backport in it's entirety, which I suppose also means I'd be fine not backporting.

If we did backport, I think only:

  • docs/docsite/rst/playbook_guide/playbooks_async.rst
  • docs/docsite/rst/network/dev_guide/developing_resource_modules_network.rst

The other changes should stay in the older branches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-2.19 Automatically create a backport for the stable-2.19 branch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants