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 31/01/2018
Date: Thu, 31 Jan 2019 16:32:25 +0000 [thread overview]
Message-ID: <63ff6808-b96f-dcdf-ab6f-0d4bf34936ed@intel.com> (raw)
Minutes 31 January 2018
-----------------------
Agenda:
* Release Dates
* 19.02 RC4 status
* 19.02 release
* Subtrees
* OvS
Participants:
* Intel
* Mellanox
* NXP
* RedHat
Release Dates
-------------
* v19.02 dates:
* RC4 released on Monday, January 28
* Release: Friday, February 1, 2019
* v19.05 dates:
* Proposal Deadline: Friday, 1 March
* RC1: Friday, 29 March
* Release: Friday, 10 May
* Roadmap web page updated accordingly:
http://core.dpdk.org/roadmap/#dates
* Contributors please provide 19.05 roadmap whenever available
* Intel & Mellanox working on sending one soon. RedHat? NXP? Marvel? others?
19.02 RC4 status
----------------
* Both Intel & Mlx test result looks good
19.02 release
-------------
* 19.02 is planned for this Friday (tomorrow)!
* Nothing major/critical expected
Subtrees
--------
* main
* There will be documentation updates
* Need to finalize deprecation notices for next release
* John will work on release notes to today/tomorrow
* A build fix merged
* next-net
* No new patch on the tree
* There are a few renaming patches target next release
* next-virtio
* No new patch on the tree
* An existing vhost deadlock patch under review, target next release
* next-crypto
* No new patch on the tree
* next-eventdev
* next-pipeline
* next-qos
* No update, we need attendance from maintainers
* Stable trees
* v18.08.1-rc3 is ready for testing, thanks to Kevin
* Stable tree RC waiting for test, anyone from community welcome to test them
send a test report or even a quick note to mail list:
* LTS: v16.11.9-rc2
* LTS: v17.11.5-rc2
* Stable: v18.08.1-rc3
* Reminder, each stable managed as a branch on stable git tree:
https://git.dpdk.org/dpdk-stable/
* Discussed sending a survey to community about stable tree usage (not LTS)
OvS
---
* In progress, no issue seen on 2.11
* Release ~3 weeks later
* '--socket-limit' & '--legacy-mem' work on master will be backported to the
2.11 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.
reply other threads:[~2019-01-31 16: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=63ff6808-b96f-dcdf-ab6f-0d4bf34936ed@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).