DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] DPDK Release Status Meeting 24/10/2019
Date: Thu, 24 Oct 2019 12:44:44 +0100	[thread overview]
Message-ID: <80d6c1d9-562d-e0c0-125e-3a4c8d48b54e@intel.com> (raw)

Minutes 24 October 2019
-----------------------

Agenda:
* Release Dates
* Subtrees
* Opens

Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat


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

* v19.11 dates:
  * Integration/Merge/RC1 date pushed to *Sunday 27 October*
  * RC2				Friday 8 November
  * RC3				Friday 15 November
  * Release			Friday 22 November

* Proposed dates for 20.02 release on the mail list, please comment
  https://mails.dpdk.org/archives/dev/2019-September/143311.html
  These dates may affected from the 19.11 delays, please review again.


Subtrees
--------

* main
  * Some features/patches will be pushed to rc2, rc1 won't be feature complete
  * Some optimization/good to have patches can be postponed to next release, to
    reduce the stress in current release, which is big, already late and the
    start of a new ABI policy.
  * eal, ABI, LTO patches are on the queue for review
  * Better to get following eal patchset for rc1, more review requested
    https://patchwork.dpdk.org/project/dpdk/list/?series=7024
  * Dynamic mbuf, RIB & FIB libs may be merged for rc1

* next-net
  * ~50 patches in backlog
  * Planning to get as much ethdev changes for rc1, remaining ones:
    * hairpin, 	Rx offloads,
      * planning to get to rc1 if all goes OK
    * extend flow metadata,
      * depends on dynamic mbuf, patch may go in depends on dynamic mbuf go into
        main repo or not
    * flow tag, LRO
      * won't go in unless reviewed/acked on time for rc1
  * PMD and testpmd patches will be merged with best of for rc1, rest will
    pushed to rc2
  * A new PMD sent after v1 deadline, ionic, postponed to next release

* next-net-crypto
  * Pull request has been sent, some patches are postponed to rc2
  * security library, CPU Crypto change is not concluded in Tech Board,
    since it is a library change if not merged for rc1, will be postponed
    next release.
  * ipsec-secgw changes are trending to be postponed to next release
  * armv8 crypto PMD discussion is still going on in the mail list
    https://mails.dpdk.org/archives/dev/2019-October/146813.html

* next-net-eventdev
  * Some more patches are in the tree waiting for pull
  * l2fwd-event app can be pushed to rc2
    (update the existing l3fwd for eventdev pushed to next release)

* next-net-virtio
  * Will merge Marvin's vhost patch for rc1
  * Maxim's (own) Virtio vDPA set pushed to next release

* next-net-intel
  * ipn3ke PMD still at risk for rc1, can be considered for rc2

* LTS
  * v18.11.3-rc2 under test
    * Target release date is tomorrow (25 October)


Opens
-----

* Luca reported a build error on master, from bnx2x

https://build.opensuse.org/package/live_build_log/home:bluca:dpdk/dpdk/Debian_10/aarch64


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 Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.

                 reply	other threads:[~2019-10-24 11:44 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=80d6c1d9-562d-e0c0-125e-3a4c8d48b54e@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).