DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: web@dpdk.org
Cc: john.mcnamara@intel.com, david.marchand@redhat.com,
	michelle.devlin@intel.com
Subject: [PATCH] update 22.11.0 schedule
Date: Thu, 10 Nov 2022 11:30:50 +0100	[thread overview]
Message-ID: <20221110103050.1427257-1-thomas@monjalon.net> (raw)

As discussed in the maintainers meeting,
the next release candidates are postponed.
We keep time for -rc4 short, so the release is not delayed too much.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 content/roadmap/_index.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/content/roadmap/_index.md b/content/roadmap/_index.md
index 103b315..9b51f72 100644
--- a/content/roadmap/_index.md
+++ b/content/roadmap/_index.md
@@ -89,8 +89,9 @@ The last period is approximately 1 month long and is dedicated to bug fixing.
 - Proposal deadline (RFC/v1 patches): 14 August 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
+- Builtin applications features freeze (-rc3): 14 November 2022
+- Last release candidate for validation (-rc4): 18 November 2022
+- Release: 23 November 2022
 
 ### Stable Releases {#stable}
 ----
-- 
2.36.1


             reply	other threads:[~2022-11-10 10:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10 10:30 Thomas Monjalon [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2022-11-03 15:56 Ferruh Yigit
2022-11-03 16:10 ` Thomas Monjalon
2022-11-03 20:07   ` Mcnamara, John
2022-11-09 17:39     ` 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=20221110103050.1427257-1-thomas@monjalon.net \
    --to=thomas@monjalon.net \
    --cc=david.marchand@redhat.com \
    --cc=john.mcnamara@intel.com \
    --cc=michelle.devlin@intel.com \
    --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).