All of lore.kernel.org
 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 29/04/2021
Date: Thu, 29 Apr 2021 12:03:17 +0100	[thread overview]
Message-ID: <YIqSdURoEeGJsE7r@silpixa00399752> (raw)

Release status meeting minutes {Date}
=====================================
:Date: 29 April 2021
:toc:

.Agenda:
* Release Dates
* -rc1 status
* Subtrees
* LTS
* Defects

.Participants:
* Broadcom
* Intel
* Marvell
* Nvidia
* Red Hat


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

* `v21.05` dates
  - -rc2:           Wednesday, 5 May
  - -rc3:           Wednesday, 12 May
  - Release pushed to *Friday, 21 May*

* 1-5 May is Labor Day holiday in PRC.

* `v21.08` draft dates, please comment:
  - Proposal/V1:    Wednesday, 2 June
  - -rc1:           Wednesday, 7 July
  - Release:        Friday, 6 August

* Expecting a small `v21.08` release.


rc1 status
----------

* Intel shared the -rc1 test results
  - http://inbox.dpdk.org/dev/SJ0PR11MB51502A2AC546E7561F331192FE5F9@SJ0PR11MB5150.namprd11.prod.outlook.com/
  - No critical or blocking issue
  - Some Bugzilla defects submitted
  - Konstantin reported an IPsec issue, in ipsec-secgw
    ** Investigation is going on, will submit a Bugzilla defect when ready


Subtrees
--------

* main
  - Quite this week, not much update
  - There is a doc patch to include code in documentation
    ** https://patches.dpdk.org/project/dpdk/patch/20210421091146.1384708-1-conor.walsh@intel.com/
    ** Waiting for more review/ack to merge
       *** Intel is planning a rework on existing documentation for this
  - meson syntax update patch merged
    ** There is another series from Bruce with a script to check the syntax
       *** https://patches.dpdk.org/project/dpdk/patch/20210426105403.226004-1-bruce.richardson@intel.com/

* next-net
  - Some fixes already merged, ~60 patches in backlog
  - Fixes in the backlog, looks OK for -rc2
  - Pulled from vendor sub-trees yesterday

* next-crypto
  - No update

* next-eventdev
  - CNXK eventdev driver for -rc2, may get a new version
  - For dlb2, techboard made a decision
    ** Waiting for new version

* next-virtio
  - Chenbo sent pull request yesterday
  - During PRC holiday Maxime will take care of the tree
  - Maxime will review patches next week

* next-net-brcm
  - A couple of patches merged, a few to follow, nothing big for release

* next-net-intel
  - No update

* next-net-mlx
  - Merged some patches, ~30 left in backlog
  - May get one more new series, but that won't be big

* next-net-mrvl
  - CNXK net driver planned for -rc2
    ** It may be postponed to next release
    ** Since driver will go via next-net, Ferruh will try to review


LTS
---

* `v19.11` (next version is `v19.11.9`)
  - Not much update at this stage

* `v20.11` (next version is `v20.11.2`)
  - Not much update at this stage


Defects
-------

* Ajit continues to follow/manage the Bugzilla
  - Bugs are under control, some new ones assigned to owners
  - Some regressions reported
  - Some fix patches sent for gcc11 errors
    ** Kevin not verified them yet
    ** Both Fedora 34 and gcc11 are released, better to support them
       *** We can take gcc11 build issues as soft-blocker for the release



.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-04-29 11:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-29 11:03 Ferruh Yigit [this message]
2021-04-29 11:08 ` [dpdk-dev] DPDK Release Status Meeting 29/04/2021 Thomas Monjalon
2021-05-04 13:46 ` Thinh Tran

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=YIqSdURoEeGJsE7r@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 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.