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.02-rc4
Date: Thu, 31 Jan 2019 09:50:45 +0000	[thread overview]
Message-ID: <AM6PR05MB592692BBB17C1EDD3520AD56C2910@AM6PR05MB5926.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <13983341.c6sE5FLPCF@xps>

Hi Thomas, 

We are ok with this release and we don't have any blocking issues. 

Kindest regards,
Raslan Darawsheh

> -----Original Message-----
> From: announce <announce-bounces@dpdk.org> On Behalf Of Thomas
> Monjalon
> Sent: Monday, January 28, 2019 4:10 AM
> To: announce@dpdk.org
> Subject: [dpdk-announce] release candidate 19.02-rc4
> 
> A new DPDK release candidate is ready for testing:
> 	https://emea01.safelinks.protection.outlook.com/?url=https%3A%2
> F%2Fgit.dpdk.org%2Fdpdk%2Ftag%2F%3Fid%3Dv19.02-
> rc4&amp;data=02%7C01%7Crasland%40mellanox.com%7C429f529d6cfe409a
> ec8e08d684c5bbcb%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C6
> 36842382145841177&amp;sdata=rDPJj%2BceNMArFLPUxRfeBtuNUwkRQTSf
> %2BrmNbwjhC%2Fw%3D&amp;reserved=0
> 
> The release notes:
> 	https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F
> %2Fdoc.dpdk.org%2Fguides%2Frel_notes%2Frelease_19_02.html&amp;data
> =02%7C01%7Crasland%40mellanox.com%7C429f529d6cfe409aec8e08d684c5
> bbcb%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C6368423821458
> 41177&amp;sdata=cJMGQNKUBiiYNKp4tdSRkobEuR3PYX88yGp4zFnbRvM%3
> D&amp;reserved=0
> 
> 42 patches (docs and fixes) were integrated.
> This is the last release candidate for DPDK 19.02.
> 
> You may share some release validation results
> by replying to this message (at dev@dpdk.org).
> If no objection, the version 19.02.0 will be out on February 1st.
> 
> If you are preparing the next release cycle, please send your v1 patches
> before the 19.05 proposal deadline, which will happen on March 1st.
> 
> PS: *CfP for India summit of March 9th is closing today!*
> 	https://emea01.safelinks.protection.outlook.com/?url=https%3A%2
> F%2Fwww.dpdk.org%2Fevent%2Fdpdk-summit-bangalore-
> 2019%2F&amp;data=02%7C01%7Crasland%40mellanox.com%7C429f529d6cf
> e409aec8e08d684c5bbcb%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0
> %7C636842382145841177&amp;sdata=o5evOjyVTOXY%2Freto%2BhmaY%2F
> MI8hCpHZcu2a6CJPIXgM%3D&amp;reserved=0
> 

      reply	other threads:[~2019-01-31  9:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28  2:10 Thomas Monjalon
2019-01-31  9:50 ` Raslan Darawsheh [this message]

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=AM6PR05MB592692BBB17C1EDD3520AD56C2910@AM6PR05MB5926.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).