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 9/5/2019
Date: Thu, 9 May 2019 11:21:34 +0100 [thread overview]
Message-ID: <1977ec28-1a94-8675-bf03-11145e00dfcc@intel.com> (raw)
Message-ID: <20190509102134.6jgdC4htan1XrJdz8-TsgBlbPuMVKCWBXKzhLk2Q55k@z> (raw)
Minutes 9 May 2019
------------------
Agenda:
* Release Dates
* RC3 status
* Subtrees
* OvS
* Conferences
* Opens
Participants:
* Arm
* Debian/Microsoft
* Intel
* Mellanox
* RedHat
Release Dates
-------------
* v19.05 dates:
* RC3 is released on Saturday, 4 May
* RC4 date pushed to: *Thursday, 9 May*
* Release date pushed to: *Monday, 13 May*
* 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
RC3 status
----------
* RC3 Intel test results looks good
* IBM sent test report to the mail list, no issue reported
* https://mails.dpdk.org/archives/dev/2019-May/131908.html
Subtrees
--------
* main
* Will pull from next-net
* Will get doc patches
* Hash library issue probably can wait
* Probably will get IPC fixes and will check timer fixes
* next-net
* Got some code changes, pulled from intel and mlx trees
* next-virtio
* No patches for rc4
* next-crypto
* There are doc patches to merge
* A few code patches can go in directly to main repo
* next-eventdev
* next-pipeline
* next-qos
* No update, we need attendance from maintainer
* Stable trees
* 18.11.2 is in progress
* Will have the -rc on 20 May
* Planning to release roughly on four weeks, it would be great to get
LTS test results within this time frame
* There is a patch that adds new device ids, should get it to LTS?
* There is no objection to backport the patch, only need to confirm
with driver maintainer that old driver supports new device ids
OvS
---
* Nothing major
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
* Reminder of the short CFP duration and deadline is approaching
* US summit dates are not fixed yet
Opens
-----
* Akhil is looking for co-maintainer for crypto sub-tree
* Where is the DTS in dpdk website. It is in:
* https://www.dpdk.org/hosted-projects/
* Defects
* We can discuss with Ajit to get defects status offline since the meeting
timing is not good for him
* Test reports
* It can be good if testers shares the test reports publicly in dev mail list
* Report can be sent as reply to -rc announce mail, but only to the dev mail
list, excluding the 'announce' mail list
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-09 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 10:21 Ferruh Yigit [this message]
2019-05-09 10:21 ` 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=1977ec28-1a94-8675-bf03-11145e00dfcc@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).