doc: remove confusing release candidate statements

Message ID 20240515110552.46458-1-thomas@monjalon.net (mailing list archive)
State New
Delegated to: Thomas Monjalon
Headers
Series doc: remove confusing release candidate statements |

Checks

Context Check Description
ci/checkpatch success coding style OK
ci/loongarch-compilation success Compilation OK
ci/loongarch-unit-testing success Unit Testing PASS
ci/Intel-compilation success Compilation OK
ci/intel-Testing success Testing PASS
ci/github-robot: build success github build: passed
ci/intel-Functional success Functional PASS
ci/iol-mellanox-Performance success Performance Testing PASS
ci/iol-intel-Performance success Performance Testing PASS
ci/iol-unit-amd64-testing success Testing PASS
ci/iol-compile-amd64-testing success Testing PASS
ci/iol-unit-arm64-testing success Testing PASS
ci/iol-broadcom-Performance success Performance Testing PASS
ci/iol-sample-apps-testing success Testing PASS
ci/iol-abi-testing success Testing PASS
ci/iol-intel-Functional success Functional Testing PASS
ci/iol-broadcom-Functional success Functional Testing PASS
ci/iol-compile-arm64-testing success Testing PASS

Commit Message

Thomas Monjalon May 15, 2024, 11:05 a.m. UTC
  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@monjalon.net>
---
 doc/guides/contributing/patches.rst | 2 --
 1 file changed, 2 deletions(-)
  

Comments

Ferruh Yigit May 16, 2024, 9:24 a.m. UTC | #1
On 5/15/2024 12:05 PM, Thomas Monjalon wrote:
> 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@monjalon.net>
>

Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
  
Thomas Monjalon June 20, 2024, 3:50 a.m. UTC | #2
16/05/2024 11:24, Ferruh Yigit:
> On 5/15/2024 12:05 PM, Thomas Monjalon wrote:
> > 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@monjalon.net>
> 
> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>

Applied
  

Patch

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@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.