From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: Minutes of Technical Board Meeting, 2022-11-30
Date: Mon, 23 Jan 2023 10:03:17 +0100 [thread overview]
Message-ID: <2325762.trqCLbgVIZ@thomas> (raw)
1/ Traces in ethdev API
It has been decided to have traces everywhere.
In datapath or in grey area (not sure how fast it should be),
we must use compile-time enabled trace for performance reason.
2/ Tech writer hiring
Hiring failed so far.
Thomas to ask explanations for recent candidates.
3/ MIT license exception
No progress at this date.
4/ UNH SOW
The accomplishments of 2022 must be categorized to fit with 2022 SOW.
The 2023 plan must be voted in a sheet during the next 2 weeks,
and it could be validated during the next meeting.
5/ Release 22.11.1 with hotfix
There is an issue for comparing ABI with 22.11.0.
We need review and testing of the hotfix for making 22.11.1.
The new tag will be the reference for ABI checks.
reply other threads:[~2023-01-23 9:03 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=2325762.trqCLbgVIZ@thomas \
--to=thomas@monjalon.net \
--cc=dev@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).