DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 9/07/2020
Date: Thu, 9 Jul 2020 11:26:07 +0100	[thread overview]
Message-ID: <c4350247-c306-6b88-6cfb-b6a69db9924e@intel.com> (raw)

Minutes 9 July 2020
-------------------

Agenda:
* Release Dates
* Subtrees
* LTS
* OvS
* Opens

Participants:
* Arm
* Debian/Microsoft
* Intel
* Marvell
* Nvidia
* NXP
* Red Hat


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

* v20.08 dates:
  * -rc1 pushed to  *Sunday, 12 July 2020*
  * -rc2:           Monday,   20 July 2020
  * Release:        Tuesday,   4 August 2020

* v20.11 proposal dates, please comment:
  * Proposal/V1:    Wednesday, 2 September 2020
  * -rc1:           Wednesday, 30 September 2020
  * -rc2:           Friday, 16 October 2020
  * Release:        Friday, 6 November 2020

  * Please remember to send roadmap for 20.11.


Subtrees
--------

* main
  * There is priority PCI issue, patch is waiting more review
    * https://patches.dpdk.org/patch/73521/
  * Following are in the backlog
    * RCU series
    * Ring cleanup
    * C11 atomics
    * FIB / hash change from Vladimir
      * Thomas will check today
    * Ethdev patches
    * If-proxy
      * Can be considered for -rc2, needs review
      * It is hard to make big changes as community
      * Needs more specific review comments to work/fix
      * There is no time for preparing the spec
        * The review and time is general problem for generic features
  * Patches for -rc2
    * Regex PMD
    * ethdev PMD updates
    * A few patches for crypto
    * Not much patches planned for -rc2, can keep the -rc2 date for now

* next-net
  * Pulled from vendor sub-trees
  * virtio, bnxt & nxp patches merged
  * There are still ethdev patches pending in backlog
    * Ethdev patches not reviewed/ready end of this week can miss the release
  * More patches expected after -rc1 from mainly vendor trees

* next-crypto
  * Read for -rc1, pulled yesterday
  * There can be a few driver patches for -rc2

* next-eventdev
  * Read for -rc1, pulled
  * Some doc patches for after -rc1

* next-virtio
  * Chenbo is managing the virtio patches during Maxime's absence
  * Ready for -rc1
  * One set postponed to next release, rest merged

* next-net-intel
  * Pulled for -rc1
  * More patches expected for -rc2

* next-net-mlx
  * Some more patches expected for -rc1
  * Can be ready today but not blocker for -rc1

* next-net-mrvl
  * pulled for -rc1
  * Some qede patches are in the backlog


LTS
---

* v18.11.9-rc2 is out, please test
  * https://mails.dpdk.org/archives/dev/2020-June/171690.html
  * Testing issues resolved
  * The release is planned for this week


OvS
---

* 2.14 soft freeze passed, it was 1 July, feature freeze is approaching


Opens
-----

* Please check Bugzilla for bugs assigned to you
  * https://bugs.dpdk.org/



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:[~2020-07-09 10: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=c4350247-c306-6b88-6cfb-b6a69db9924e@intel.com \
    --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).