61b36c6f30
* Fix changelog link title. * Rename Ansible 2.10 and 2.11 porting guides to Ansible-base porting guides. * Add stub for automatically generated 2.10 porting guide. * Move things that should not be in the ansible-base porting guide to the ansible porting guide. * Apply changes to base porting guides. * Add remark that ansible-base is mainly for developers. * Ansible Base -> Ansible-base * Fix link in base porting guide. * Add generated porting guide. * Use same header signs as antsibull-changelog's RST builder. * Update generated porting guide.
25 lines
744 B
ReStructuredText
25 lines
744 B
ReStructuredText
.. _porting_guides:
|
|
|
|
**********************
|
|
Ansible Porting Guides
|
|
**********************
|
|
|
|
This section lists porting guides that can help you in updating playbooks, plugins and other parts of your Ansible infrastructure from one version of Ansible to the next.
|
|
|
|
Please note that this is not a complete list. If you believe any extra information would be useful in these pages, you can edit by clicking `Edit on GitHub` on the top right, or raising an issue.
|
|
|
|
.. toctree::
|
|
:maxdepth: 1
|
|
:glob:
|
|
|
|
porting_guide_base_2.11
|
|
porting_guide_2.10
|
|
porting_guide_base_2.10
|
|
porting_guide_2.9
|
|
porting_guide_2.8
|
|
porting_guide_2.7
|
|
porting_guide_2.6
|
|
porting_guide_2.5
|
|
porting_guide_2.4
|
|
porting_guide_2.3
|
|
porting_guide_2.0
|