[PATCH] doc: remove confusing release candidate statements

[Thomas Monjalon]

The help of "dpdk-next-*" repositories is welcome at all stages,
except maybe during the last release candidate.
Better to remove statements about a time limit,
and let decisions happen on the fly.

Signed-off-by: Thomas Monjalon <thomas at monjalon.net>
---
 doc/guides/contributing/patches.rst | 2 --
 1 file changed, 2 deletions(-)

diff --git a/doc/guides/contributing/patches.rst b/doc/guides/contributing/patches.rst
index 7605ea4d64..04c66bebc4 100644
--- a/doc/guides/contributing/patches.rst
+++ b/doc/guides/contributing/patches.rst
@@ -25,8 +25,6 @@ The DPDK development process has the following features:
 * Patches are reviewed publicly on the mailing list.
 * Successfully reviewed patches are merged to the repository.
 * Patches should be sent to the target repository or sub-tree, see below.
-* All sub-repositories are merged into main repository for ``-rc1`` and ``-rc2`` versions of the release.
-* After the ``-rc2`` release all patches should target the main repository.
 
 The mailing list for DPDK development is `dev at dpdk.org <https://mails.dpdk.org/archives/dev/>`_.
 Contributors will need to `register for the mailing list <https://mails.dpdk.org/listinfo/dev>`_ in order to submit patches.
-- 
2.45.0