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 055F4A034F; Mon, 7 Feb 2022 14:31:36 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id E6D8D410F3; Mon, 7 Feb 2022 14:31:35 +0100 (CET) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) by mails.dpdk.org (Postfix) with ESMTP id 4DF3B410EA for ; Mon, 7 Feb 2022 14:31:34 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailout.west.internal (Postfix) with ESMTP id CB7F03201FC6; Mon, 7 Feb 2022 08:31:32 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Mon, 07 Feb 2022 08:31:33 -0500 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:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; bh=7ePxicHU7xWD7n sFbp+zvUdhoLyNjQBjqRatmUW0aIg=; b=q05enDFkw31Syj51cspSMR6BhLJOkl YQdmw0jiFzQaOo6K8n+XpWeFyii6iWYG0tH6rxadHKzkBx3Rqna9U6GBahsqzQXA lYKO3drnElsItaLxrhtnBDNZBEFselyjw6tv0EYKlrwUkmrCV5dcmF4lpmPxNaqv 1P2nxabga0AhnjJR2pswTIia+peyJn7wplrRFs4zgoOHfSH1FjzdoZYWMFxkrFGc sElhb+QuNwD6hXcWRdkioUk5VoNWuro5Vut+T49FsbocLo5LwyDTghkmyVm6iauf 3FCQ7GgxuuEQR7SuXPdbwqAEvEG8znzXMw+VrVsk3yhBgOhBIAIZ7JdQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=7ePxicHU7xWD7nsFbp+zvUdhoLyNjQBjqRatmUW0a Ig=; b=e+zmFOMqliM1UbroI5XK2S70FMDjE9CcdfGYnvgYWQsd7WQ9liYObagWY Xurnm1YiHDQW8YWwImHKnezVt+Kmki+FkZB7/lfexCMeE6IVrGtPyKOZpF30Xc28 vQkc/XU9f7AwzsFH/ZE9sM2Ek/ERgdHWhU/pqv4kaGzYbjHR+YZytqWHZdRas2sC 9Lz22hk/v7ZTyrW04MbCKiEzyoNSgZv/IXd9n2p6c3+iSz55MomvW2AK5RGVPBUk 8+8vHeB7x80UFE3VEEUgIyV33bDSZTCD8doW6dtwDjPAJrGPHxLmqG+XQKImcIxV mFjnMqLYrq7q1PVu9Lfryv93tPB7A== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrheehgdehudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefhvffufffkjghfggfgtgesthfuredttddtvdenucfhrhhomhepvfhhohhmrghs ucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenucggtf frrghtthgvrhhnpedugefgvdefudfftdefgeelgffhueekgfffhfeujedtteeutdejueei iedvffegheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 7 Feb 2022 08:31:31 -0500 (EST) From: Thomas Monjalon To: Ferruh Yigit Cc: john.mcnamara@intel.com, david.marchand@redhat.com, jerinj@marvell.com, maxime.coquelin@redhat.com, ajit.khaparde@broadcom.com, gakhil@marvell.com, web@dpdk.org Subject: Re: [PATCH] update 22.03.0 schedule Date: Mon, 07 Feb 2022 14:31:29 +0100 Message-ID: <4375032.LvFx2qVVIh@thomas> In-Reply-To: <8176cf15-4572-0f1d-83d1-181a19ba8d51@intel.com> References: <20220203110925.1639700-1-thomas@monjalon.net> <5791629.lOV4Wx5bFT@thomas> <8176cf15-4572-0f1d-83d1-181a19ba8d51@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org 07/02/2022 14:25, Ferruh Yigit: > On 2/7/2022 1:21 PM, Thomas Monjalon wrote: > > 03/02/2022 14:25, Thomas Monjalon: > >> 03/02/2022 12:18, Ferruh Yigit: > >>> On 2/3/2022 11:09 AM, Thomas Monjalon wrote: > >>>> As discussed in the maintainers meeting, > >>>> the release candidates are pushed by 2 days. > >>>> > >>> > >>> Only -rc1 date was discussed, but do you think will it have > >>> knock-on effect to other release candidates? > >>> No objection from my end, just asking to clarify. > >> > >> Indeed we did not clarify the impact on -rc2 and -rc3 in the meeting. > >> I think we should keep the same amount of time for -rc2 and -rc3, > >> and squeeze in the last week before the release. > >> Opinions? > >> > >>>> -- API freeze (-rc1): 9 February 2022 > >>>> -- PMD features freeze (-rc2): 23 February 2022 > >>>> -- Builtin applications features freeze (-rc3): 2 March 2022 > >>>> +- API freeze (-rc1): 11 February 2022 > >>>> +- PMD features freeze (-rc2): 25 February 2022 > >>>> +- Builtin applications features freeze (-rc3): 4 March 2022 > >>>> - Release: 11 March 2022 > > > > Do we agree on these dates? > > > > > > OK for me, > I am for merging ASAP so community can be aware of the -rc1 date change. Merged with this (modified) explanation: " As discussed in the maintainers meeting, the -rc1 date is pushed by 2 days. Other release candidates are also pushed by 2 days. " If any objection arise we can still change.