From: Patrick Robb <probb@iol.unh.edu>
To: dev <dev@dpdk.org>
Cc: dts@dpdk.org, ci@dpdk.org
Subject: DTS WG Meeting Minutes - November 21, 2024
Date: Sun, 15 Dec 2024 23:12:21 -0500 [thread overview]
Message-ID: <CAJvnSUCa=7_sNut15+3b3iJs+DDfaRMFKGPnvFLmFo-OrhyEiQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2763 bytes --]
#####################################################################
November 21, 2024
Attendees
* Patrick Robb
* Paul Szczepanek
* Luca Vizzarro
#####################################################################
Minutes
=====================================================================
General Discussion
* 24.11 roadmap status:
https://docs.google.com/document/d/1doTZOOpkv4D5P2w6K7fEJpa_CjzrlMl3mCeDBWtxnko/edit
* We should work on the 25.03 roadmap at the DTS meeting in 2 weeks.
Patrick will come prepared with a rough draft.
* 24.11 RC3 has released
* Next-dts was pulled, and we are not applying any additional patches
for the 24.11 release
* Do not push anything to next-dts until the release of 24.11 (excluding
any bugfixes)
* Our major framework goals were included in this release (pydantic,
prebuilt binaries, detailed results.json)
* We added ~5 new testsuites, including l2fwd, blocklist, dynamic
config, checksum offload
* UNH can start to run these in it’s CI lab
* There will be no CI meeting next Thursday due to the American
Thanksgiving holiday
=====================================================================
Patch discussions
* Meson –werror settings was being passed to Sphinx -W (treat warnings as
errors) inadvertently. Luca provided a bugfix which Thomas merged:
https://git.dpdk.org/dpdk/commit/?id=f4ccce58c1a33cb41e1e820da504698437987efc
* Luca will work on addin ruff linting
* No docs are generated for the testsuite docstrings, so they are not
validated, but if they were Sphinx would complain about some issues which
are present.
* Testsuite Docstrings:
* For 25.03, we will rewrite our testsuite docstrings to use the “Steps”
and “Verify” categories (currently used in a subset of testsuites)
* Luca will pick up the task of upgrading scapy and mypy to improve type
checking (brought in with a recent scapy version)
=====================================================================
Bugzilla discussions
* Action item: Patrick needs to clean up the list now that RC3 has been
released
=====================================================================
Any other business
* There are some small inaccuracies throughout the framework docstrings due
to framework updates which have come in from 24.07 and 24.11, where the
corresponding docstring updates were missed
* Part of the reason for this is that multiple things are documented in
2 places, which we should stop doing going forward
* UNH guys should each volunteer to review docstrings for a certain set
of framework dirs/files early in the 25.03 release cycle and submit
docstring updates to bring everything up to date
* Next meeting Dec 5, 2024
[-- Attachment #2: Type: text/html, Size: 3056 bytes --]
reply other threads:[~2024-12-16 4:14 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='CAJvnSUCa=7_sNut15+3b3iJs+DDfaRMFKGPnvFLmFo-OrhyEiQ@mail.gmail.com' \
--to=probb@iol.unh.edu \
--cc=ci@dpdk.org \
--cc=dev@dpdk.org \
--cc=dts@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).