DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: announce@dpdk.org
Subject: release candidate 22.07-rc4
Date: Tue, 12 Jul 2022 00:36:36 +0200	[thread overview]
Message-ID: <6125682.jrt8l4j9yI@thomas> (raw)

A new DPDK release candidate is ready for testing:
	https://git.dpdk.org/dpdk/tag/?id=v22.07-rc4

There are 22 new patches in this snapshot.

Release notes:
	https://doc.dpdk.org/guides/rel_notes/release_22_07.html

This is the last release candidate.
Only documentation should be updated before the release.

Reviews of deprecation notices are required:
https://patches.dpdk.org/bundle/dmarchand/deprecation_notices/

You may share some release validation results
by replying to this message at dev@dpdk.org
and by adding tested hardware in the release notes.

Please think about sharing your roadmap now for DPDK 22.11.

Thank you everyone



             reply	other threads:[~2022-07-11 22:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11 22:36 Thomas Monjalon [this message]
2022-07-12  9:32 ` Jiang, YuX
2022-07-12  9:44   ` Xia, Chenbo
2022-07-14  8:17     ` Jiang, YuX
2022-07-15  7:59       ` Jiang, YuX
2022-07-15 14:18 ` Thinh Tran
2022-07-17 14:33 ` Wael Abualrub

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=6125682.jrt8l4j9yI@thomas \
    --to=thomas@monjalon.net \
    --cc=announce@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).