DPDK patches and discussions
 help / color / mirror / Atom feed
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 11/7/2019
Date: Thu, 11 Jul 2019 11:30:53 +0100	[thread overview]
Message-ID: <1560a37e-dbcf-6cd8-2210-a4f23c036bef@intel.com> (raw)

Minutes 11 July 2019
--------------------

Agenda:
* Release Dates
* RC1 Status
* Subtrees
* OvS
* Opens


Participants:
* Arm
* Debian/Microsoft
* Intel
* Mellanox
* Red Hat


Release Dates
-------------

* v19.08 dates:
  * RC1 is released on Monday 08 July
    * https://mails.dpdk.org/archives/announce/2019-July/000269.html
  * RC2		Friday 19 July
  * Release	Thurs  01 August

* v19.11 dates:
  * Proposal/V1               Friday 06 September 2019
  * Integration/Merge/RC1     Friday 11 October   2019
  * Release                   Friday 08 November  2019


RC1 Status
----------

* Intel test results are mostly OK, no critical issue found
  * Two build errors reported, patches sent for both

* Two changes expected in main repo *after* RC1, please be aware of them
  and make testing plans related to them:

  * Interrupt fix, PMD link interrupt handlers may be affected
    * Already merged

  * IOVA fix to fix octeontx issues
    * Needs review, will be merged today/tomorrow


Subtrees
--------

* main
  * On track for RC2
  * Some NXP patches sent late most probably will be pushed to 19.11

* next-net
  * Some existing PMD patches will be considered for RC2
  * Only a few ethdev library patches won't able to make RC1, most probably
    they will be postponed to next release

* next-virtio
  * Tiwei pushed a patch, pulled by next-net

* next-crypto
  * No update, but there were some patches target the RC2

* next-eventdev
  * No update

* Stable trees
  * No update


OvS
---

* Soft freeze done for 2.12 on 7th Monday, since it has been done a week later
than usual, hard freeze pushed to 22 July.


Opens
-----

* Will discuss offline Bugzilla maintenance


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-07-11 10:31 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=1560a37e-dbcf-6cd8-2210-a4f23c036bef@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).