minor #16881 New features must go on the 6.x branch (alexislefebvre)

javiereguiluz · javiereguiluz · commit 2c92fa00efe3 · 2022-06-16T16:43:47.000+02:00
This PR was merged into the 4.4 branch. Discussion ---------- New features must go on the 6.x branch This is consistent with the PR template: https://github.com/symfony/symfony/blob/6.2/.github/PULL_REQUEST_TEMPLATE.md --- Is there something like a variable that could be used instead of hardcoding these versions? Commits ------- ffda951 New features must go on the 6.x branch
diff --git a/contributing/code/pull_requests.rst b/contributing/code/pull_requests.rst
@@ -129,7 +129,7 @@ work:
   </contributing/code/maintenance>` (you may have to choose a higher branch if
   the feature you are fixing was introduced in a later version);
 
-* ``5.x``, if you are adding a new feature.
+* ``6.x``, if you are adding a new feature.
 
   The only exception is when a new :doc:`major Symfony version </contributing/community/releases>`
   (5.0, 6.0, etc.) comes out every two years. Because of the
@@ -142,7 +142,7 @@ work:
     All bug fixes merged into maintenance branches are also merged into more
     recent branches on a regular basis. For instance, if you submit a PR
     for the ``4.4`` branch, the PR will also be applied by the core team on
-    the ``5.x`` branch.
+    the ``5.x`` and ``6.x`` branches.
 
 Create a Topic Branch
 ~~~~~~~~~~~~~~~~~~~~~
