From: Luca Boccassi <bluca@debian.org>
To: dpdk stable <stable@dpdk.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] 16.11.8 (LTS) patches review and test
Date: Thu, 23 Aug 2018 09:55:39 +0100 [thread overview]
Message-ID: <1535014539.5764.128.camel@debian.org> (raw)
In-Reply-To: <20180813182103.28045-1-luca.boccassi@gmail.com>
On Mon, 2018-08-13 at 19:21 +0100, luca.boccassi@gmail.com wrote:
> Hi all,
>
> Here is a list of patches targeted for LTS release 16.11.8. Please
> help review and test. The planned date for the final release is
> August
> the 23rd.
> 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=v16.11.8-rc1
>
> These patches are located at branch 16.11 of dpdk-stable repo:
> https://dpdk.org/browse/dpdk-stable/
>
> Thanks.
>
> Luca Boccassi
Hi,
Regression tests from Intel have highlighted a possible issue with the
changes (unidentified as of now), so while investigation is in progress
we decided to postpone the release to Monday the 27th to be on the safe
side.
Apologies for any issues this might cause.
--
Kind regards,
Luca Boccassi
next prev parent reply other threads:[~2018-08-23 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 18:21 luca.boccassi
2018-08-20 6:46 ` [dpdk-dev] [dpdk-stable] " Marco Varlese
2018-08-20 8:46 ` Luca Boccassi
2018-08-20 8:46 ` [dpdk-dev] " Luca Boccassi
2018-08-23 8:55 ` Luca Boccassi [this message]
2018-08-27 16:17 ` Luca Boccassi
2018-08-29 9:55 ` Luca Boccassi
2018-08-29 10:58 ` Marco Varlese
2018-08-29 13:28 ` Marco Varlese
2018-08-29 13:36 ` [dpdk-dev] [dpdk-stable] " Luca Boccassi
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=1535014539.5764.128.camel@debian.org \
--to=bluca@debian.org \
--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).