From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3131244035; Wed, 15 May 2024 13:06:07 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EE3F14025C; Wed, 15 May 2024 13:06:06 +0200 (CEST) Received: from wfout1-smtp.messagingengine.com (wfout1-smtp.messagingengine.com [64.147.123.144]) by mails.dpdk.org (Postfix) with ESMTP id CF3814021D for ; Wed, 15 May 2024 13:06:04 +0200 (CEST) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.west.internal (Postfix) with ESMTP id 8CC1D1C00092; Wed, 15 May 2024 07:06:03 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Wed, 15 May 2024 07:06:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to; s=fm3; t=1715771163; x=1715857563; bh=IeCXSmAd8Pov7ReN2wM+n gMnKCop4PhydfKS0KUIh3o=; b=gAh0HMpg8HzpVdZP2K5TxCxDAhk7k2F17yFyG U0nV9OM78kvjWyl2+CI2fe/XsQtVD09N074hZwrA0/exZebMhpUsiDIujV8QDsRI wRBSvd40oA6SKGxzYLpsnrQd7DillqZ6+dgpAlQsWK1RYClOQRQmqggydeB+XSQH 6jvSvyUegWxJXZ8A80tkgSr4Aif0A6kx+qZE0g6oklo2butx70Uo0fEBcgug7vsi 1spbDJ4TEUCfxnlTRhpLU2Kovrhk3gJPB0jaRa40WcXFtq4G6y6svBGTA4mwnIbs RHmtsvu9A28ky8Tf14JoOQBVywIrtwVbzaG0jyXaSjuE68rww== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:message-id:mime-version:reply-to:subject:subject:to :to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; t=1715771163; x=1715857563; bh=IeCXSmAd8Pov7ReN2wM+ngMnKCop 4PhydfKS0KUIh3o=; b=gMIxdUkuVxdkygFibLbWpGGTA32Yf//QNvtLtxNyys1h P8hGObGnrhoTqqVyAOOTx2Zh5mhWVlt+nj5yniAlYoOrlGzhfCue+P53A2qxyQGX 4svKA0UsW8gBJlZWpYRrDkITs9KZFcykb44s+T+E10Nq48bJ2+5EfHng+W9OC9fs FC3yXY30iFug2qqd/dHNzpZCjfP8/QGGL/et4evVjqoImd4dkjtKSQJDPxu19ctj KQZ32TQoJCbBNkp9fiQd4+/5epsnJ6NKHvY5P5E1p9OWh19FUr1deSdEXcHG96fA XDL2bX6bQffAQrQ6RxFhSe/Vw6DvgUPw1obeAToPOw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdegkedgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefhvfevufffkffoggfgsedtkeertd ertddtnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepvdetgfffvdeuueegfeehke etfeelhffhtdejfeetjeettdetgfdthedvteetheeunecuffhomhgrihhnpeguphgukhdr ohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpe hthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 15 May 2024 07:06:02 -0400 (EDT) From: Thomas Monjalon To: dev@dpdk.org Cc: david.marchand@redhat.com Subject: [PATCH] doc: remove confusing release candidate statements Date: Wed, 15 May 2024 13:05:52 +0200 Message-ID: <20240515110552.46458-1-thomas@monjalon.net> X-Mailer: git-send-email 2.45.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 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 --- 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@dpdk.org `_. Contributors will need to `register for the mailing list `_ in order to submit patches. -- 2.45.0