From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [PATCH 1/3] update release dates for 23.11
Date: Thu, 16 Nov 2023 11:33:43 +0100 [thread overview]
Message-ID: <20231116103408.88053-2-thomas@monjalon.net> (raw)
In-Reply-To: <20231116103408.88053-1-thomas@monjalon.net>
Update effective release dates for 23.11 cycle.
Final release should happen on 23 November or the next day.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
content/roadmap/_index.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 51acb4f..f106623 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -113,10 +113,10 @@ The last period is approximately 1 month long and is dedicated to bug fixing.
#### 23.11
- Proposal deadline (RFC/v1 patches): 12 August 2023
-- API freeze (-rc1): 11 October 2023
-- PMD features freeze (-rc2): 27 October 2023
-- Builtin applications features freeze (-rc3): 3 November 2023
-- Release: 15 November 2023
+- API freeze (-rc1): 17 October 2023
+- PMD features freeze (-rc2): 6 November 2023
+- Builtin applications features freeze (-rc3): 14 November 2023
+- Release: 23 November 2023
### Stable Releases {#stable}
----
--
2.42.0
next prev parent reply other threads:[~2023-11-16 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 10:33 [PATCH 0/3] roadmap dates Thomas Monjalon
2023-11-16 10:33 ` Thomas Monjalon [this message]
2023-11-16 10:33 ` [PATCH 2/3] add roadmap dates for 24.03 cycle Thomas Monjalon
2023-11-16 10:33 ` [PATCH 3/3] complete estimated release dates for 2024 Thomas Monjalon
2023-11-16 11:56 ` [PATCH 0/3] roadmap dates Mcnamara, John
2023-11-16 12:09 ` Thomas Monjalon
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=20231116103408.88053-2-thomas@monjalon.net \
--to=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).