update backport instructions (#2183)

Author: samccann

docs/docsite/rst/community/development_process.rst

@@ -21,10 +21,7 @@ If you want to follow the conversation about what features will be added to ``an
 * the :ref:`roadmaps`
 * the :ref:`Ansible Release Schedule <release_and_maintenance>`
 * the :ref:`ansible-core project branches and tags <core_branches_and_tags>`
-* various GitHub `projects <https://github.com/ansible/ansible/projects>`_ - for example:
-
-   * the `2.17 release project <https://github.com/ansible/ansible/projects/48>`_
-   * the `core documentation project <https://github.com/orgs/ansible/projects/94/views/1>`_
+* the `2.19 release project <https://github.com/orgs/ansible/projects/140>`_
 
 
 .. _community_pull_requests:
@@ -206,7 +203,7 @@ Here are some examples:
       remote_src=True even if mode was not set as a parameter.  This failed on
       filesystems which do not have permission bits (https://github.com/ansible/ansible/issues/29444).
 
-You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.17/changelogs/fragments>`_ for the 2.17 release.
+You can find more example changelog fragments in the `changelog directory <https://github.com/ansible/ansible/tree/stable-2.18/changelogs/fragments>`_ for the 2.18 release.
 
 After you have written the changelog fragment for your PR, commit the file and include it with the pull request.
 
@@ -241,7 +238,7 @@ We do **not** backport features.
 
    These instructions assume that:
 
-    * ``stable-2.17`` is the targeted release branch for the backport
+    * ``stable-2.18`` is the targeted release branch for the backport
     * ``https://github.com/ansible/ansible.git`` is configured as a ``git remote`` named ``upstream``. If you do not use a ``git remote`` named ``upstream``, adjust the instructions accordingly.
     * ``https://github.com/<yourgithubaccount>/ansible.git`` is configured as a ``git remote`` named ``origin``. If you do not use a ``git remote`` named ``origin``, adjust the instructions accordingly.
 
@@ -250,7 +247,7 @@ We do **not** backport features.
 .. code-block:: shell
 
        git fetch upstream
-       git checkout -b backport/2.17/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.17
+       git checkout -b backport/2.18/[PR_NUMBER_FROM_DEVEL] upstream/stable-2.18
 
 #. Cherry pick the relevant commit SHA from the devel branch into your feature branch, handling merge conflicts as necessary:
 
@@ -264,15 +261,15 @@ We do **not** backport features.
 
 .. code-block:: shell
 
-       git push origin backport/2.17/[PR_NUMBER_FROM_DEVEL]
+       git push origin backport/2.18/[PR_NUMBER_FROM_DEVEL]
 
-#. Submit the pull request for ``backport/2.17/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.17`` branch
+#. Submit the pull request for ``backport/2.18/[PR_NUMBER_FROM_DEVEL]`` against the ``stable-2.18`` branch
 
 #. The Release Manager will decide whether to merge the backport PR before the next minor release. There isn't any need to follow up. Just ensure that the automated tests (CI) are green.
 
 .. note::
 
-    The branch name ``backport/2.17/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches.
+    The branch name ``backport/2.18/[PR_NUMBER_FROM_DEVEL]`` is somewhat arbitrary but conveys meaning about the purpose of the branch. This branch name format is not required, but it can be helpful, especially when making multiple backport PRs for multiple stable branches.
 
 .. note::