DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raslan Darawsheh <rasland@mellanox.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-announce] release candidate 19.05-rc4
Date: Mon, 13 May 2019 12:10:58 +0000	[thread overview]
Message-ID: <DB3PR0502MB3964A61513AFAEFD4A52A69EC20F0@DB3PR0502MB3964.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190513121058.gCabqKcUQKtqGuc5WVfnXeLzY7bcGP6qTbooDtGJIbA@z> (raw)
In-Reply-To: <3010866.ptfx1ugjOl@xps>

Hi Thomas,

We've tested rc4 in Mellanox and we are only missing one patch:
http://patches.dpdk.org/patch/53382/
which is a major blocking for running MLX5 with failsafe PMD.

Kindest regards,
Raslan Darawsheh

> -----Original Message-----
> From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> Monjalon
> Sent: Friday, May 10, 2019 2:35 AM
> To: announce@dpdk.org
> Subject: [dpdk-announce] release candidate 19.05-rc4
> 
> A new DPDK release candidate is ready for testing:
> 	https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fgit.dpdk.org%2Fdpdk%2Ftag%2F%3Fid%3Dv19.05-
> rc4&amp;data=02%7C01%7Crasland%40mellanox.com%7Cc08188a6d40e47b4
> 653608d6d4d70139%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C6
> 36930417239759124&amp;sdata=nKerNkxVWQRJhKexTZC%2BqfDmJfOZxwf
> wBJ8HkOQKfJ0%3D&amp;reserved=0
> 
> The release notes:
> 	https://eur03.safelinks.protection.outlook.com/?url=http%3A%2F%2
> Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_19_05.html&amp;data=0
> 2%7C01%7Crasland%40mellanox.com%7Cc08188a6d40e47b4653608d6d4d701
> 39%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636930417239759
> 124&amp;sdata=XMrk5qZOSIYABCxwkRDus%2F6FGT0m0ziJJPIVMbO2Yy8%3
> D&amp;reserved=0
> 
> 41 patches (docs and fixes) were integrated.
> This is the last release candidate for DPDK 19.05.
> 
> You may share some release validation results by replying to this message (at
> dev@dpdk.org).
> If no objection, the version 19.05.0 will be out on May 13.
> 
> The deprecation notices for 19.08 may still be reviewed during the last days
> of this release cycle.
> 
> If you are preparing the next release cycle, please send your v1 patches
> before the 19.08 proposal deadline, which will happen on June 3.
> It is also time to build an estimated roadmap for the next cycles.
> 
> PS: The CfP for Europe conference of September is closing at the end of May
> 	https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%
> 2Fwww.dpdk.org%2Fevent%2Fdpdk-userspace-
> bordeaux%2F&amp;data=02%7C01%7Crasland%40mellanox.com%7Cc08188a
> 6d40e47b4653608d6d4d70139%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0
> %7C0%7C636930417239759124&amp;sdata=Ksjc%2Fxmb12FfGNlm2je%2Bh0
> Ak27nIExgHKLDmOoK299o%3D&amp;reserved=0
> 
> 


  parent reply	other threads:[~2019-05-13 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-09 23:35 Thomas Monjalon
2019-05-09 23:35 ` Thomas Monjalon
2019-05-11 17:46 ` dwilder
2019-05-11 17:46   ` dwilder
2019-05-13 12:10 ` Raslan Darawsheh [this message]
2019-05-13 12:10   ` Raslan Darawsheh
2019-05-14 15:30 ` Ju-Hyoung Lee
2019-05-14 15:30   ` Ju-Hyoung Lee

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=DB3PR0502MB3964A61513AFAEFD4A52A69EC20F0@DB3PR0502MB3964.eurprd05.prod.outlook.com \
    --to=rasland@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=thomas@monjalon.net \
    /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).