Message ID | 20220203110925.1639700-1-thomas@monjalon.net (mailing list archive) |
---|---|
State | Accepted |
Headers |
Return-Path: <web-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id E21F9A00C2; Thu, 3 Feb 2022 12:09:39 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C8A8B406B4; Thu, 3 Feb 2022 12:09:39 +0100 (CET) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by mails.dpdk.org (Postfix) with ESMTP id 836554068B for <web@dpdk.org>; Thu, 3 Feb 2022 12:09:38 +0100 (CET) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 29C765C01AE; Thu, 3 Feb 2022 06:09:36 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Thu, 03 Feb 2022 06:09:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm3; bh=mAwSUMh+olWkFhyGu9Xax2k6g2SKjFwtXKINt3gh3vU=; b=FB5MQ aBsMunRJ9tnjQ59plXNfeL8lb19nOUvioowx8LyJ+LiZuaAqm1fOITGG1J7YNjQA RUHzqntV82qpoBRgs/rd7uvThxl44cYoJHOccbCzPQThff1XaaE9VOm2pTd8zVuU jBHAxq0/d7q0a0PoJGcW9fjYFfonPILPtfYuM0r1c3916h6vv7KqeqU0cA8ClLci YGA/QfEGr9EQ13hgcvHYWm6k404TYUCl5E3x+1R5VBdGI5fi+b8WVok9bj6La1Ll gVcQslg7WnpgvrfePaKgclIb4ATfCqNoWe0xnzfj47lGJD7L3ZSC2PfDHDsVO6zW M5uY3rtaiwMdNmvhg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding:date:date :from:from:in-reply-to:message-id:mime-version: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=mAwSUMh+olWkFhyGu9Xax2k6g2SKj FwtXKINt3gh3vU=; b=FyK0Q6ELfhPPdT4xFSoMJH3MhdBgQhEwXMmhKhYCtDCQb cTZ3xhp0zNpmAQrlJp37I5E3KCDpW1BsnCIyQVpvWIy0DE7VjbZDudrQiJwpmoH1 BN4UjkvkuvFeOkGqifGN6vnNi1UMlGjPL///D8qY+Gad+rKxu5R3J43Mketw7jqa HsltkG6/Ton4sjOXJ0WJfJv3OjcsVjz5R1PWzYkKUtgU0B/fe1syU4pyxOu3iw6s GQdGtaTejDSyi1i8xN9bhPnYIC++PqbMIsV/gbx+GCAWSsCABJJRGkHmcKFLza3q mGVvOXZlI++qaE/vsFReYaA3EH684qg4lW0ht5iFQ== X-ME-Sender: <xms:77f7Yf15Qa7B5pOeQIf6UJUo7wnE0DcDbPchuBfHugejSLUIZu4xLw> <xme:77f7YeFarCiUoSnYqZuHKDifVClzXNtQuJ5Dr0TxzofqLUKfiYGwO8ApJP56lm13F 6sl__2LoT_oD0WVAA> X-ME-Received: <xmr:77f7Yf4v1QeAWe2HtilxO7NzI_6YRbLDr1INfq-XImxehO9ihPk0km2NSVe6Tf0ohSAgTki8tP00fw6XW8h7caodTsRkGjY> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrgeejgddvvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkffoggfgsedtkeertdertd dtnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehmohhn jhgrlhhonhdrnhgvtheqnecuggftrfgrthhtvghrnhepvdelvdduhedvudduveeuvdevhe egudelgeeigfejheduhedttdegudffjeeihffgnecuvehluhhsthgvrhfuihiivgeptden ucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: <xmx:77f7YU0P76Xb64mw-9ErAKMt3hPpKMtIXwWLzMGHJCNUMLK_aWtbxA> <xmx:77f7YSF2yIsR5mc9mFoM3R4_odB70nc8-fu8xyc-JmMelTIsEjDHQA> <xmx:77f7YV-OzqNpTl--SqtZeKo1KWkV_eLYJE_1jn3Ml-7lMBAZud1orw> <xmx:8Lf7YXTGxdT2GewD8tcxrZlQjCmOilrsPM8IVORvMcA5F5QsNXrk-A> Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 3 Feb 2022 06:09:34 -0500 (EST) From: Thomas Monjalon <thomas@monjalon.net> To: web@dpdk.org Cc: john.mcnamara@intel.com, david.marchand@redhat.com, ferruh.yigit@intel.com Subject: [PATCH] update 22.03.0 schedule Date: Thu, 3 Feb 2022 12:09:25 +0100 Message-Id: <20220203110925.1639700-1-thomas@monjalon.net> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK website maintenance <web.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/web>, <mailto:web-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/web/> List-Post: <mailto:web@dpdk.org> List-Help: <mailto:web-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/web>, <mailto:web-request@dpdk.org?subject=subscribe> Errors-To: web-bounces@dpdk.org |
Series |
update 22.03.0 schedule
|
|
Commit Message
Thomas Monjalon
Feb. 3, 2022, 11:09 a.m. UTC
As discussed in the maintainers meeting,
the release candidates are pushed by 2 days.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Comments
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. > Signed-off-by: Thomas Monjalon <thomas@monjalon.net> > --- > content/roadmap/_index.md | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md > index 9d3f8e6..9d372c8 100644 > --- a/content/roadmap/_index.md > +++ b/content/roadmap/_index.md > @@ -95,9 +95,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing. > #### 22.03 > > - Proposal deadline (RFC/v1 patches): 31 December 2021 > -- 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 > > #### 22.07
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
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?
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.
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.
> 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? > +1
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md index 9d3f8e6..9d372c8 100644 --- a/content/roadmap/_index.md +++ b/content/roadmap/_index.md @@ -95,9 +95,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing. #### 22.03 - Proposal deadline (RFC/v1 patches): 31 December 2021 -- 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 #### 22.07