DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Subject: Minutes of Technical Board Meeting, 2026-07-22
Date: Thu, 23 Jul 2026 18:26:28 +0100	[thread overview]
Message-ID: <amJOxBOjChh7AmJG@bricha3-mobl1.ger.corp.intel.com> (raw)

Techboard meeting was brief, due to a low attendance because of holidays.

NOTE: Next techboard meeting due on 5th August has been CANCELLED because
many TB members will be available.

Next meeting will be on Wednesday 19th August.

Agenda
------

No discussion as such. A number of updates were given:

* Thomas provided an update on the 26.07 release:
  - Code has been tagged
  - Release will be generally available later today
* There are discussions ongoing, including with LF from legal side, about a
  potential new CI system for Grout project
  - Expectation is that systems in a lab will be provided for the CI work
  - Not directly relevant to main DPDK, but to wider project and
    ecosystem - Grout specifically.
  - More details will be available once it is all finalized
* For DPDK CI, David gave a reminder that for 26.11 release cycle, ABI checks
  are not required
  - Lincoln reported that his team was already aware of this and prepared to 
    disable the checks
* Aaron reported that he is investigating getting help for DPDK in managing
  security reports
  - University of Massachusetts has expertise in this area
  - Investigating if we can get budget to get some students in the security
    area to provide help to DPDK project.


                 reply	other threads:[~2026-07-23 17:26 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=amJOxBOjChh7AmJG@bricha3-mobl1.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --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