From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dpdk-dev <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>,
"Stokes, Ian" <ian.stokes@intel.com>,
Thomas Monjalon <thomas@monjalon.net>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
"Akhil, Goyal" <akhil.goyal@nxp.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>,
Qian Xu <qian.q.xu@intel.com>, Yongseok Koh <yskoh@mellanox.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Qi Zhang <qi.z.zhang@intel.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] DPDK Release Status Meeting 2/5/2019
Date: Thu, 2 May 2019 17:30:27 +0100 [thread overview]
Message-ID: <113b42f4-6206-a7f2-7313-5922a9a98ade@intel.com> (raw)
Message-ID: <20190502163027.hNley3DkH2IXVvCZBmnE9pRiOLAMJKUeXYJU4ZLyzzQ@z> (raw)
Minutes 2 May 2019
------------------
Agenda:
* Release Dates
* RC2 status
* Subtrees
* OvS
* Conferences
* Opens
Participants:
* Debian
* Intel
* Mellanox
* RedHat
Release Dates
-------------
* v19.05 dates, RC3 date pushed to Friday, 3 May:
* RC3: *Friday, 3 May*
* RC4: Wednesday, 8 May
* Release: Friday, 10 May
* May 1-4 inclusive is holiday in PRC, Intel testing won't be
available during that time
* v19.08 dates:
* Proposal/V1 Monday 03 June 2019
* Integration/Merge/RC1 Monday 01 July 2019
* Release Thurs 01 August 2019
* Schedule updated on roadmap page:
https://core.dpdk.org/roadmap/
* v19.11 proposed dates, *please comment*,
* Proposal/V1 Friday 06 September 2019
* Integration/Merge/RC1 Friday 11 October 2019
* Release Friday 08 November 2019
* Constrains:
* PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
* US DPDK Summit on mid November, better to have release before summit
RC2 status
----------
* RC2 Intel test results looks good, no major issue detected
Subtrees
--------
* main
* RCU library is merged
* There is a avx512 related defect waiting
* There are more fixes to merge
* next-net
* A few fixes, no major issue, will be ready for rc3
* next-virtio
* No patches for rc3
* next-crypto
* pulled into main repository yesterday
* There are a few more fixes from Bruce
* next-eventdev
* 2 patches merged directly into main repo
* next-pipeline
* next-qos
* No update, we need attendance from maintainer
* Stable trees
* 18.11.2 is in progress
OvS
---
* For OvS testing on DPDK Community Lab, which branch to test leaning to:
DPDK: "master" branch,
OvS: "dpdk-latest" branch which will be rebased monthly on "master" branch
* Tested 17.11.6-rc1 (with OvS 2.10 & 2.9), no issues found so far
Conferences
-----------
* DPDK Userspace summit: DPDK Userspace · Sept. 19-20, 2019
https://www.dpdk.org/event/dpdk-userspace-bordeaux/
* CFP Opens: Monday, April 29
* CFP Closes: Friday, May 24
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree
* There is a demand on backporting driver features into stable releases,
should discuss more with community
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.
next reply other threads:[~2019-05-02 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-02 16:30 Ferruh Yigit [this message]
2019-05-02 16:30 ` Ferruh Yigit
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=113b42f4-6206-a7f2-7313-5922a9a98ade@intel.com \
--to=ferruh.yigit@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ian.stokes@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qian.q.xu@intel.com \
--cc=shahafs@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yskoh@mellanox.com \
/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).