DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Subject: [PATCH] update 23.07 schedule
Date: Tue, 20 Jun 2023 17:47:50 +0200	[thread overview]
Message-ID: <20230620154750.280502-1-thomas@monjalon.net> (raw)

As discussed in the maintainers meeting,
adjust rc2/rc3 dates because of the delay in rc1.

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 b377893..29f7479 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -105,9 +105,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing.
 #### 23.07
 
 - Proposal deadline (RFC/v1 patches): 22 April 2023
-- API freeze (-rc1): 7 June 2023
-- PMD features freeze (-rc2): 21 June 2023
-- Builtin applications features freeze (-rc3): 28 June 2023
+- API freeze (-rc1): 12 June 2023
+- PMD features freeze (-rc2): 23 June 2023
+- Builtin applications features freeze (-rc3): 30 June 2023
 - Release: 12 July 2023
 
 #### 23.11
-- 
2.41.0


                 reply	other threads:[~2023-06-20 15:48 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=20230620154750.280502-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).