From: Ruifeng Wang <Ruifeng.Wang@arm.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>,
bluca@debian.org, nd@arm.com
Subject: Re: DPDK Release Status Meeting 2023-11-23
Date: Sun, 26 Nov 2023 09:55:02 +0800 [thread overview]
Message-ID: <b252b287-6a50-45e9-84ba-dca07f606b8b@arm.com> (raw)
In-Reply-To: <PH8PR11MB6804D5FD084BFED316132CC7FCB8A@PH8PR11MB6804.namprd11.prod.outlook.com>
On 2023/11/24 4:53 PM, Mcnamara, John wrote:
> Release status meeting minutes 2023-11-23
>
<snip>
> issues:
>
> * Build/link issue on Debian
>
> https://salsa.debian.org/debian/dpdk/-/jobs/4949787
>
> * cpfl compilation issue
>
>
> https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_Next/i586
>
> * LCOREs autotest timing out on ARM:
>
>
> https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_12/aarch64
The failure relates to test environment. 50s is not enough for lcores
test to finish.
Due to a relative bigger RTE_MAX_LCORE value on ARM, the unit test case
would take a longer time to finish iterations.
In one of my run, the case took about 100s.
>
> Proposed Schedule for 2023
>
> --------------------------
>
> See http://core.dpdk.org/roadmap/#dates
>
> LTS
>
> ---
>
> * 22.11.3 - In progress
>
> * 21.11.6 - In progress
>
> * 20.11.10 - In progress
>
> * 19.11.15 - Will only be updated with CVE and critical fixes.
>
> * Distros
>
> * Debian 12 contains DPDK v22.11
>
> * Ubuntu 22.04-LTS contains DPDK v21.11
>
> * Ubuntu 23.04 contains DPDK v22.11
>
> Defects
>
> -------
>
> * Bugzilla links, 'Bugs', added for hosted projects
>
> * https://www.dpdk.org/hosted-projects/
>
> DPDK Release Status Meetings
>
> ----------------------------
>
> The DPDK Release Status Meeting is intended for DPDK Committers to
> discuss the
>
> status of the master tree and sub-trees, and for project managers to track
>
> progress or milestone dates.
>
> The meeting occurs on every Thursday at 9:30 UTC over Jitsi on
> https://meet.jit.si/DPDK
>
> You don't need an invite to join the meeting but if you want a calendar
> reminder just
>
> send an email to "John McNamara john.mcnamara@intel.com" for the invite.
>
next prev parent reply other threads:[~2023-11-26 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 8:53 Mcnamara, John
2023-11-26 1:55 ` Ruifeng Wang [this message]
2023-11-26 12:44 ` Luca Boccassi
2023-11-27 2:51 ` Ruifeng Wang
2023-11-27 10:13 ` Thomas Monjalon
2023-11-27 17:16 ` Stephen Hemminger
2023-11-28 5:53 ` Ruifeng Wang
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=b252b287-6a50-45e9-84ba-dca07f606b8b@arm.com \
--to=ruifeng.wang@arm.com \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=nd@arm.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 NNTP newsgroup(s).