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 6/02/2020
Date: Thu, 6 Feb 2020 10:32:47 +0000 [thread overview]
Message-ID: <a0015f73-4e13-7ae9-839b-84954ed35a10@intel.com> (raw)
Minutes 6 February 2020
-----------------------
Agenda:
* Release Dates
* Subtrees
* OvS
Participants:
* Intel
* Marvell
* Mellanox
* NXP
* Red Hat
Release Dates
-------------
* v20.02 dates:
* -rc2 pushed to *Thursday 6 February 2020*
* -rc3 pushed to *Friday 14 February 2020*
* Release pushed to *Friday 21 February 2020*
* Release pushed because of extended PRC holidays
* v20.05 dates:
* Proposal/V1: Friday 6 March 2020
* Integration/Merge/RC1: Friday 10 April 2020
* Release: Friday 1 May 2020
Subtrees
--------
* main
* Pulled next-net & next-net-crypto
* Dropped two patches from crypto because of ABI breakages
* ccp sha3 & chacha20-poly
* ABI check patches merged
* In travis checks enabled by default
* next-net
* pulled, nothing in backlog for -rc3, there can be fixes
* next-net-crypto
* ipsecgw eventmode can be postponed, Akhil will check
* CPU crypto patches merged
* next-net-eventdev
* There can be a few fixes for -rc3
* next-net-virtio
* Three small fixes for -rc3
* next-net-mlx
* pulled
* LTS
* 17.11.10-rc1 released, please test and report results
* https://mails.dpdk.org/archives/dev/2020-January/154915.html
* Got test results from Intel, Red Hat & Mellanox
* QAT regression reported by Intel testing, need help from developers
* mlx reported regressions, needs more details
* Will wait two more week for above issues clarified
* Rough release date is mid February
* 18.11.6 released
* https://mails.dpdk.org/archives/dev/2020-January/156760.html
OvS
---
* Release on track
* Backporting removing experimental tag under discussion in DPDK
* https://mails.dpdk.org/archives/dev/2020-January/155419.html
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:[~2020-02-06 10:32 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=a0015f73-4e13-7ae9-839b-84954ed35a10@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).