DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 20/05/2021
Date: Thu, 20 May 2021 13:15:05 +0100	[thread overview]
Message-ID: <YKZSyX8NJuMZ4fY5@silpixa00399752> (raw)

Release status meeting minutes {Date}
=====================================
:Date: 20 May 2021
:toc:

.Agenda:
* Release Dates
* -rc3/4 status
* Subtrees
* LTS
* Defects
* Opens

.Participants:
* Arm
* Broadcom
* Canonical
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat


Release Dates
-------------

* `v21.05` dates
  - -rc4 is released on Wednesday, 19 May
    ** http://inbox.dpdk.org/dev/1994252.qWktbAlWXN@thomas/
  - Release:        Friday, 21 May

* `v21.08` dates
  - Proposal/V1:    Wednesday, 2 June
  - -rc1:           Monday, 5 July
  - Release:        Tuesday, 3 August

* *Please send roadmaps*, preferably before beginning of the release

* Expecting a small `v21.08` release.


rc3/4 status
------------

* -rc3 test results
  - Intel, IBM, Nvidia & Broadcom shared the -rc3 test results, nothing critical
    ** http://inbox.dpdk.org/dev/7142607.3L8AUzOtay@thomas/t/#u

* The -rc4 is new, no test reports yet.

* Good to get more test results, please share the test reports


Subtrees
--------

* main
  - More tooling and doc patches in the backlog
    ** John will help on finalizing release notes
  - Testing latest DPDK with OvS & SPDK, looks good
  - There are four deprecation notices needs to be closed today, please review
    ** vdpa: https://patches.dpdk.org/project/dpdk/patch/20210518073441.2749096-1-thomas@monjalon.net/
    ** crypto: https://patches.dpdk.org/project/dpdk/patch/20210414201544.1063413-1-thomas@monjalon.net/
    ** Windows: https://patches.dpdk.org/project/dpdk/patch/20210310235421.23259-1-dmitry.kozliuk@gmail.com/
    ** net: https://patches.dpdk.org/project/dpdk/patch/20210303225121.16146-1-dmitry.kozliuk@gmail.com/
  - v21.05 supports gcc11, Kevin will add a release notes update for it
    ** Kevin also verified the clang 12
    ** Should LTS release support gcc11?

* next-net
  - No patches for the release

* next-crypto
  - There is a doc path from Pablo under review
  - Deprecation notice patch from Thomas
    ** http://dpdk.org/patch/91473

* next-eventdev
  - There is one fix for dlb2
    ** It is waiting new version, patch should be split into multiple patches
       *** Internal review before upstream may help

* next-virtio
  - Some regressions fixed in -rc4
  - vhost crash fixed
    ** https://bugs.dpdk.org/show_bug.cgi?id=703
  - No patches for the release

* next-net-brcm
  - No patches for the release, maybe doc update

* next-net-intel
  - No patches for the release

* next-net-mlx
  - Some fixes merged, all clear for release

* next-net-mrvl
  - No patches in the backlog


LTS
---

* `v19.11` (next version is `v19.11.9`)
  - Backport request email sent
    ** http://inbox.dpdk.org/stable/bab7aa8d-fb62-332e-68a8-474ade5c2451@intel.com/
  - Planning an -rc next week

* `v20.11` (next version is `v20.11.2`)
  - "Xueming(Steven) Li" requested support for backporting some commits
    ** http://inbox.dpdk.org/stable/28797869-b83a-fba8-5c85-8527e4107ac4@intel.com/
  - Planning an -rc soon

* Distros
  - v20.11 in Debian 11
  - v20.11 in Ubuntu 21.04


Defects
-------

* Bugzilla links, 'Bugs',  added for hosted projects
  - https://www.dpdk.org/hosted-projects/


Opens
-----

* Cheng is working on the security issues, it is progressing

* DPDK is using IRC for community communication and we are using https://freenode.net/
  servers. There are some discussions around freenode: https://www.kline.sh/
  - Will wait for two weeks to get things clarified, will discuss again later
  - Maxime registered a DPDK channel in https://libera.chat/ for any case

* Coverity is running regularly
  - Can we have out of cycle run for -rc4? Last run was yesterday.
  - We need a way to verify coverity issues before merging it, will carry topic
    to CI mail list an Aaron

* There is a new DPDK blog series, Faces of DPDK, starting with Dmitry:
  - https://www.dpdk.org/news/blog/



.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 Thursdays at 8:30 UTC. on https://meet.jit.si/DPDK

If you wish to attend just send an email to
"John McNamara <john.mcnamara@intel.com>" for the invite.
*****

                 reply	other threads:[~2021-05-20 12:15 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=YKZSyX8NJuMZ4fY5@silpixa00399752 \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --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).