DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
	"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 15/07/2021
Date: Thu, 15 Jul 2021 22:28:25 +0000	[thread overview]
Message-ID: <SN6PR11MB30867A10D12324C68F7BC464FC129@SN6PR11MB3086.namprd11.prod.outlook.com> (raw)

Release status meeting minutes {Date}
=====================================
:Date: 15 July 2021
:toc:

.Agenda:
* Release Dates
* Subtrees
* Roadmaps
* LTS
* Defects
* Opens

.Participants:
* ARM
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* Red Hat


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

* `v21.08` dates
  - Proposal/V1:    Wednesday, 2 June  (completed)
  - rc1:            Saturday,  10 July (completed)
  - rc2:            Thursday,  22 July
  - rc3:            Thursday,  29 July
  - Release:        Tuesday,   3 August

* Note: We need to hold to the early August release date since
  several of the maintainers will be on holidays after that.

* `v21.11` dates (proposed and subject to discussion)
  - Proposal/V1:    Friday, 10 September
  - -rc1:           Friday, 15 October
  - Release:        Friday, 19 November

Subtrees
--------

* main
  - RC1 released.
  - RC2 targeted for Thursday 22 July.
  - Still waiting update on Solarflare patches.


* next-net
  - No update.

* next-crypto
  - 4 new PMDs in this release:
    ** CNXK - merged.
    ** MLX - on last review. Should be merged for RC2.
    ** Intel QAT - Should be merged for RC2.
    ** NXP baseband - will be deferred to next release.

* next-eventdev
  - PR for RC2 today or tomorrow.

* next-virtio
  - Some patches in PR today.
  - New DMA Dev work complicates merging of some of the vhost patches.
    An offline meeting will be held to view options and decide the
    best technical approach. Maxime to set up.

* next-net-brcm
  - No update.

* next-net-intel
  - No update.

* next-net-mlx
  - PR not pulled due to comments that need to be addressed.
  - New version sent today.

* next-net-mrvl
  - Almost ready for RC2.
  - 1 or 2 small series and bug fixes.


LTS
---

* `v19.11` (next version is `v19.11.9`)
  - RC4 tagged.
  - Target release date July 19.

* `v20.11` (next version is `v20.11.3`)
  - 20.11.2 released by Xueming Li on July 7.
  - https://git.dpdk.org/dpdk-stable/commit/?h=20.11&id=a86024748385423306aac45524d6fc8d22ea6703

* 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
-----

* There in an ongoing inititive around ABI stability which was
  discussed in the Tech Board call. A workgroup has come up
  with a list of critical and major changes required to let us
  extend the ABI without as much disruption. For example:

  ** export driver interfaces as internal
  ** hide more structs (may require uninlining)
  ** split big structs + new feature-specific functions Major
  ** remove enum maximums
  ** reserved space initialized to 0
  ** reserved flags cleared

* We need to fill details and volunteers in this table:
  https://docs.google.com/spreadsheets/d/1betlC000ua5SsSiJIcC54mCCCJnW6voH5Dqv9UxeyfE/edit?usp=sharing




.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-07-15 22:28 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=SN6PR11MB30867A10D12324C68F7BC464FC129@SN6PR11MB3086.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.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).