All of lore.kernel.org
 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>,
	"david.marchand@redhat.com" <david.marchand@redhat.com>
Subject: DPDK Release Status Meeting 2023-01-19
Date: Tue, 24 Jan 2023 10:33:51 +0000	[thread overview]
Message-ID: <PH8PR11MB68049F3F914019218D4E42CFFCC99@PH8PR11MB6804.namprd11.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3381 bytes --]

Release status meeting minutes 2023-01-19
=========================================

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

Participants:
* AMD
* ARM
* Debian/Microsoft [No]
* Intel
* Marvell
* Nvidia
* Red Hat



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

The following are the proposed current dates for 23.03:


* V1:      25 December 2022
* RC1:      8 February 2023
* RC2:      1 March    2023
* RC3:      8 March    2023
* Release: 20 March    2023


Subtrees
--------

* next-net
  * Patches being merged but slowly
  * rte_flow has a lot of changes in this release and needs support
  * Some reviews ongoing but we are missing reviewer support on this tree.

* next-net-intel
  * No update.

* next-net-mlx
  * No update.

* next-net-mvl
  * Nearly all patches merged. Ready for pull.

* next-eventdev
  * Nearly all patches merged. Waiting for some review comments

  3 sets of patches from Intel.
  * Some CNXK updates

* next-baseband
  * New tree from this release.
  * Some series merged and some under review.

* next-virtio
  * Not many series under review.
  * Vhost async and VDPA patches need review.

* next-crypto
  * Some patches merged this week.
  * Build patches for QAT
  * PDCP (Packet Data Convergence Protocol) new library targeted for this release
  * Patch for CCP driver from last release

* main
  * Thread API from Tyler under review
  * ABI check merged
  * ML Dev patches need review
  * CNI (Container Network Interface) for the AF_XDP driver.
    * Will update patch to include explanation/docs.
  * Request for Roadmaps



Proposed Schedule for 2023
--------------------------

See also http://core.dpdk.org/roadmap/#dates

23.03
  * Proposal deadline (RFC/v1 patches): 25 December 2022
  * API freeze (-rc1): 8 February 2023
  * PMD features freeze (-rc2): 1 March 2023
  * Builtin applications features freeze (-rc3): 8 March 2023
  * Release: 20 March 2023

23.07
  * Proposal deadline (RFC/v1 patches): 15 April 2023
  * API freeze (-rc1): 31 May 2023
  * PMD features freeze (-rc2): 21 June 2023
  * Builtin applications features freeze (-rc3): 28 June 2023
  * Release: 12 July 2023

23.11
  * Proposal deadline (RFC/v1 patches): 12 August 2023
  * API freeze (-rc1): 29 September 2023
  * PMD features freeze (-rc2): 20 October 2023
  * Builtin applications features freeze (-rc3): 27 October 2023
  * Release: 15 November 2023

Other
-----

* TBA

LTS
---

Next releases will be:

* 22.11.1

* 21.11.4

* 20.11.8

* 19.11.15?
  * CVE and critical fixes only.



* Distros
  * v20.11 in Debian 11
  * Ubuntu 22.04 contains 21.11

Defects
-------

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


Opens
-----

* None


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 Thursday at 9:30 UTC over Jitsi on https://meet.jit.si/DPDK

You don't need an invite to join the meeting but if you want a calendar reminder just
send an email to "John McNamara john.mcnamara@intel.com" for the invite.



[-- Attachment #2: Type: text/html, Size: 18068 bytes --]

                 reply	other threads:[~2023-01-24 10:34 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=PH8PR11MB68049F3F914019218D4E42CFFCC99@PH8PR11MB6804.namprd11.prod.outlook.com \
    --to=john.mcnamara@intel.com \
    --cc=david.marchand@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.