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 25/4/2019
Date: Thu, 25 Apr 2019 14:15:10 +0100 [thread overview]
Message-ID: <cf142dc0-326d-b8dc-7ca8-417fa913fa44@intel.com> (raw)
Message-ID: <20190425131510.pnn9U8Cs3Ja3F0-qiUilfpHL8wCTGzgBx2B0uXeXt6E@z> (raw)
Minutes 25 April 2019
---------------------
Agenda:
* Release Dates
* RC2 status
* Subtrees
* OvS
* Opens
Participants:
* Debian
* Intel
* Marvell
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.05 dates, RC3 date pushed to Thursday, 2 May:
* RC2 is released on Monday, 22 April
* RC3: *Thursday, 2 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 will be merged after validated by NXP, Marvell & Intel
* next-net
* A few fixes, no major issue
* next-virtio
* No patches for rc3
* next-crypto
* Akhil get some fix + doc patches today/tomorrow
* ipsec-secgw sample app patches won't able to make the release
* next-eventdev
* No patches for rc3
* next-pipeline
* next-qos
* No update, we need attendance from maintainer
* Stable trees
* 18.11.2 is in progress, ~120 fixes merged
OvS
---
* OvS master/2.11.x release moved to 18.11.1
* For DPDK 17.11, OvS is testing 17.11.6-rc1
* For OvS testing on DPDK Community Lab, there is a discussion about having
a test branch
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree
* Static analysis:
* There are new defects with rc2, but overall number of defects are reducing
* John is looking for a way to automate lgtm.com findings
* A patch to fix all document spelling errors has been sent by John,
there will be new version of it before 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 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-04-25 13:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 13:15 Ferruh Yigit [this message]
2019-04-25 13:15 ` 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=cf142dc0-326d-b8dc-7ca8-417fa913fa44@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).