From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [PATCH] update 23.11-rc1 schedule
Date: Fri, 29 Sep 2023 17:53:00 +0200 [thread overview]
Message-ID: <20230929155300.3988786-1-thomas@monjalon.net> (raw)
As discussed in the maintainers meeting,
postpone rc1 date by almost 2 weeks.
http://mails.dpdk.org/archives/dev/2023-September/277955.html
Next release candidates are moved by 1 week.
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 e553c3f..51acb4f 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -113,9 +113,9 @@ 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): 29 September 2023
-- PMD features freeze (-rc2): 20 October 2023
-- Builtin applications features freeze (-rc3): 27 October 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
### Stable Releases {#stable}
--
2.42.0
reply other threads:[~2023-09-29 15:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230929155300.3988786-1-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).