DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kevin Traynor <ktraynor@redhat.com>
To: "Walker, Benjamin" <benjamin.walker@intel.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] 18.08.1 patches review and test
Date: Wed, 6 Mar 2019 17:36:47 +0000	[thread overview]
Message-ID: <0eb188df-95ea-3593-d621-804f99679801@redhat.com> (raw)
In-Reply-To: <3cc591055fc0d582a1bdc29e01649e163fbd0685.camel@intel.com>

On 06/03/2019 16:45, Walker, Benjamin wrote:
> On Wed, 2019-01-30 at 16:27 +0000, Kevin Traynor wrote:
>> Hi all,
>>
>> Here is a list of patches targeted for stable release 18.08.1. Please
>> help review and test. The tentative date for the final release is 28,
>> February. Before that, please shout if anyone has objections with these
>> patches being applied.
>>
>> Also for the companies committed to running regression tests,
>> please run the tests and report any issue before the release date.
>>
>> A release candidate tarball can be found at:
>>
>>     https://dpdk.org/browse/dpdk-stable/tag/?id=v18.08.1-rc3
>>
>> These patches are located at branch 18.08 of dpdk-stable repo:
>>     https://dpdk.org/browse/dpdk-stable/
>>
>> Thanks.
>>
>> Kevin Traynor
> 
> What is the current targeted release date for 18.08.1? I ask because there are
> people looking to package SPDK 18.10, which depends on DPDK 18.08, but needs
> several of the fixes queued up here to function fully.
> 

Hi Ben,

So far only one company has run regression tests and reported results on
the RC (pass). I am waiting to hear back from some others before
release. There is a maintainers call tomorrow where I will be asking
about status of validation, so may have a clearer idea after that.

Thanks for asking/sharing, it is good to know if there is a pull for a
release because sometimes it is not clear.

Kevin.

> Thanks,
> Ben
> 

  reply	other threads:[~2019-03-06 17:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-30 16:27 Kevin Traynor
2019-03-06 16:45 ` Walker, Benjamin
2019-03-06 17:36   ` Kevin Traynor [this message]
2019-03-07 11:18     ` Kevin Traynor
2019-03-22 16:56 ` Kevin Traynor
2019-03-22 16:56   ` Kevin Traynor
  -- strict thread matches above, loose matches on Subject: below --
2018-12-21 10:48 Kevin Traynor
2018-12-20 11:37 Kevin Traynor
2018-12-26  7:31 ` Shreyansh Jain

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=0eb188df-95ea-3593-d621-804f99679801@redhat.com \
    --to=ktraynor@redhat.com \
    --cc=benjamin.walker@intel.com \
    --cc=dev@dpdk.org \
    --cc=stable@dpdk.org \
    /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).