From: "lihuisong (C)" <lihuisong@huawei.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"Marchand, David" <david.marchand@redhat.com>
Subject: Re: DPDK Release Status Meeting 2024-05-09
Date: Thu, 9 May 2024 19:22:14 +0800 [thread overview]
Message-ID: <edfbea88-a78a-2b7f-9a06-bd160f93fa7d@huawei.com> (raw)
In-Reply-To: <PH8PR11MB680406810878E228F74AD063FCE62@PH8PR11MB6804.namprd11.prod.outlook.com>
Hi John and all,
在 2024/5/9 16:46, Mcnamara, John 写道:
>
> Release status meeting minutes 2024-05-09
>
> =========================================
>
> Agenda:
>
> * Release Dates
>
> * Subtrees
>
> * Roadmaps
>
> * LTS
>
> * Defects
>
> * Opens
>
> Participants:
>
> * AMD
>
> * ARM
>
> * Intel
>
> * Marvell
>
> * Nvidia
>
> * Red Hat
>
> Release Dates
>
> -------------
>
> The following are the current/updated working dates for 24.07:
>
> - Proposal deadline (RFC/v1 patches): 26 April 2024
>
> - API freeze (-rc1): 7 June 2024
>
> - PMD features freeze (-rc2): 21 June 2024
>
> - Builtin applications features freeze (-rc3): 28 June 2024
>
> - Release: 10 July 2023
>
> https://core.dpdk.org/roadmap/#dates
>
> Subtrees
>
> --------
>
> * next-net
>
> * New Napatech PMD.
>
> * next-net-intel
>
> * Some patches applied from last release.
>
> * There will be a number of base code updates
>
> in this release.
>
> * next-net-mlx
>
> * Starting to merge some patches.
>
> * next-net-mvl
>
> * Starting to review patches. No merges yet.
>
> * next-eventdev
>
> * Starting to review patches. No merges yet.
>
> * next-baseband
>
> * No update.
>
> * next-virtio
>
> * No update.
>
> * next-crypto
>
> * No update on tree.
>
> * ~40 patches in backlog.
>
> * main
>
> * Looking at changes for Graph library.
>
> * Ongoing changes for Windows.
>
> - Several series.
>
> * New DMA driver from Marvell
>
> * Note, we are looking for new maintainers for Bonding and Failsafe.
>
I volunteer to maintain the bonding driver.
>
> * 24.07 Proposed dates:
>
> - Proposal deadline (RFC/v1 patches): 26 April 2024
>
> - API freeze (-rc1): 7 June 2024
>
> - PMD features freeze (-rc2): 21 June 2024
>
> - Builtin applications features freeze (-rc3): 28 June 2024
>
> - Release: 10 July 2023
>
<...>
>
prev parent reply other threads:[~2024-05-09 11:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 8:46 DPDK Release Status Meeting 2024-05-09 Mcnamara, John
2024-05-09 11:22 ` lihuisong (C) [this message]
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=edfbea88-a78a-2b7f-9a06-bd160f93fa7d@huawei.com \
--to=lihuisong@huawei.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=thomas@monjalon.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).