From: Ferruh Yigit <ferruh.yigit@amd.com>
To: <web@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>,
David Marchand <david.marchand@redhat.com>,
John McNamara <john.mcnamara@intel.com>
Subject: [PATCH] update 22.11.0 schedule
Date: Thu, 3 Nov 2022 15:56:39 +0000 [thread overview]
Message-ID: <20221103155639.2708926-1-ferruh.yigit@amd.com> (raw)
As discussed in the maintainers meeting,
updated -rc3 date, delayed around 10 days.
Updated -rc1 & -rc2 dates to reflect actual release dates:
-rc1: https://inbox.dpdk.org/announce/13255994.nUPlyArG6x@thomas/T/#u
-rc2: https://inbox.dpdk.org/announce/6919521.aoefvbuG5b@thomas/T/#u
Signed-off-by: Ferruh Yigit <ferruh.yigit@amd.com>
---
Cc: Thomas Monjalon <thomas@monjalon.net>
Cc: John McNamara <john.mcnamara@intel.com>
---
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 f6ab19d43b33..103b3154f99a 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -87,9 +87,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing.
#### 22.11
- Proposal deadline (RFC/v1 patches): 14 August 2022
-- API freeze (-rc1): 3 October 2022
-- PMD features freeze (-rc2): 24 October 2022
-- Builtin applications features freeze (-rc3): 31 October 2022
+- API freeze (-rc1): 11 October 2022
+- PMD features freeze (-rc2): 1 November 2022
+- Builtin applications features freeze (-rc3): 10 November 2022
- Release: 16 November 2022
### Stable Releases {#stable}
--
2.25.1
next reply other threads:[~2022-11-03 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 15:56 Ferruh Yigit [this message]
2022-11-03 16:10 ` Thomas Monjalon
2022-11-03 20:07 ` Mcnamara, John
2022-11-09 17:39 ` Thomas Monjalon
2022-11-10 10:30 Thomas Monjalon
2022-11-10 10:37 ` Devlin, Michelle
2022-11-10 14:26 ` Ferruh Yigit
2022-11-11 23:44 ` Thomas Monjalon
2022-11-11 11:15 ` Mcnamara, John
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20221103155639.2708926-1-ferruh.yigit@amd.com \
--to=ferruh.yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
--cc=web@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).